[Desktop-packages] [Bug 1888458] [NEW] text not displaying ubuntu 20.04
Public bug reported: * Have upgraded from Ubuntu 10.10 to Ubuntu 20.04 * Rebooted PC * After reboot, and login * Opened gnome-terminal * something displays, but it is NOT Text * completely unreadable (screen shot attached) * with no terminal, I'm restricted in what I may do to trouble shoot this problem. * Nvidia graphics -- Updating to latest available: nvidia-driver-440, did not help GNOME-TERMINAL not working for this Ubuntu 20.04 installation ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: character-set display font unreadable ** Attachment added: "BUG__Gnome-Terminal_window_Ubuntu-20-04.png" https://bugs.launchpad.net/bugs/1888458/+attachment/5394767/+files/BUG__Gnome-Terminal_window_Ubuntu-20-04.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1888458 Title: text not displaying ubuntu 20.04 Status in gnome-terminal package in Ubuntu: New Bug description: * Have upgraded from Ubuntu 10.10 to Ubuntu 20.04 * Rebooted PC * After reboot, and login * Opened gnome-terminal * something displays, but it is NOT Text * completely unreadable (screen shot attached) * with no terminal, I'm restricted in what I may do to trouble shoot this problem. * Nvidia graphics -- Updating to latest available: nvidia-driver-440, did not help GNOME-TERMINAL not working for this Ubuntu 20.04 installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1888458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879702] Re: The software properties screen freezes when I update the software cache
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1879702 Title: The software properties screen freezes when I update the software cache Status in software-properties package in Ubuntu: Expired Bug description: I am currently using Ubuntu 20.04, but I had the same problem in 19.10. When I make changes to the software resources, when closing the program, "Update the software cache?" I come across the question. If I say yes, it updates the cache but the window freezes. It cannot be closed in any way. 'lsb_release -rd': Description: Ubuntu 20.04 LTS Release: 20.04 'apt-cache policy software-properties': software-properties: Installed: (none) Candidate: (none) Release schedule: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 16:08:11 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2017-06-10 (1075 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/local/bin/python3.7, Python 3.7.2, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-05-11 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1879702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879362] Re: image viewer long display png file and then fall xorg
[Expired for eog (Ubuntu) because there has been no activity for 60 days.] ** Changed in: eog (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1879362 Title: image viewer long display png file and then fall xorg Status in eog package in Ubuntu: Expired Bug description: it takes a very long time to display the png file. then xorg crashes and a session login window appears. if this error is not resolved soon I will be forced to switch to Microsoft Windows. Sorry but i must work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: eog 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 18:17:47 2020 InstallationDate: Installed on 2020-04-26 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1879362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880095] Re: Keyboard entry stopped working
[Expired for compiz (Ubuntu) because there has been no activity for 60 days.] ** Changed in: compiz (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1880095 Title: Keyboard entry stopped working Status in compiz package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I was toggling between text entry languages when the keyboard entry suddenly stopped working. Even the onscreen keyboard was not able to entry any keys. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-all (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 22 09:18:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2012-03-23 (2981 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE 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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri May 22 09:13:46 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1880095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876489] Re: Xorg freeze
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1876489 Title: Xorg freeze Status in xorg-server package in Ubuntu: Expired Bug description: I am dealing with freezing issues. When I did install Linux from a USB stick, it did freeze in the installation process, so I did the run installation in safe mode (taught changing drivers will help). After Linux is installed, So when I boot up ubuntu, it sometimes(70%) freezes after login, and also it sometimes freezes while I am using it. Sometimes I even can't get to log in before it stacks. Then I need to do a hard reset. Also sound sometimes is not working. I did try to change Nvidia drivers. First I did use 440 drivers. Problem with Nvidia 440 driver second monitor not detected. I did try change to xorg opensource driver it shows black screen after boot - Stops on vendor logo. At the moment I am using Nvidia 435 driver it is working, but freezes a lot. I did try to add nomodeset in grub file - GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset". Then built-in desktop freezes before login with hp logo, bet when I add a second display, Linux work on a second display. Also, in Nvidia settings when I set to performance mode, if I put a power saver, it uses integrated graphics(Intel HD 630), and the second monitor is not detected then. I did have ubuntu 19.04 and did work ok on this laptop, but I would like to use 20.04. Any suggestions? Thanks. I am booting dual boot with windows. Alos battery life is very bad, 3x times worse than windows. I am using TLP, but it doest seem to help a lot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 19:58:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.132, 5.4.0-26-generic, x86_64: installed nvidia, 390.132, 5.4.0-28-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:8519] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8519] InstallationDate: Installed on 2020-04-27 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Spectre x360 Convertible 15-df0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=0ccbd646-0752-4cae-98bb-f816acbd2666 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: AMI dmi.bios.version: F.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8519 dmi.board.vendor: HP dmi.board.version: 11.72 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.40:bd11/27/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn8519:rvr11.72:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df0xxx dmi.product.sku: 4UU78EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1876489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1880095] Re: Keyboard entry stopped working
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1880095 Title: Keyboard entry stopped working Status in compiz package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I was toggling between text entry languages when the keyboard entry suddenly stopped working. Even the onscreen keyboard was not able to entry any keys. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-all (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 22 09:18:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2012-03-23 (2981 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE 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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri May 22 09:13:46 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1880095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888425] Re: Ubuntu Freezy - Probably Gnome-Shell Bug
After the next freeze (and reboot) please run: journalctl -b-1 > prevboot.txt lspci -k > lspcik.txt and then attach the resulting two text files here. Please also follow these instructions in case the freeze is a consequence of something crashing: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** 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/1888425 Title: Ubuntu Freezy - Probably Gnome-Shell Bug Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have got a Ryzen 7 2700X, Nvidia GTX 1080 Ti and 16 GB RAM. Ubuntu sometimes freezes and I can't do nothing. I need to reboot the system pressing reset button. Usually Ubuntu (I think that Gnome-shell) freezes when I am selecting a game in Steam. When I select one game and change to another selecting the other, Ubuntu freezes. But it doesn't happen always. I read that could be a problem with Ryzen CPUs, but I don't know. Sorry and thanks for your time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 21 22:11:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (87 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.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/1888425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886644] Re: SRU the current 3.36.4 stable update
Hello Sebastien, or anyone else affected, Accepted evolution-data-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /evolution-data-server/3.36.4-0ubuntu1 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: evolution-data-server (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1886644 Title: SRU the current 3.36.4 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1886644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886644] Re: SRU the current 3.36.4 stable update
Additionally: since this includes a security fix, should there be a fix in focal-security? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1886644 Title: SRU the current 3.36.4 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1886644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
I fear the answer here might be for you to avoid using gnome-shell and use a more constrained window manager to get the behaviour you want. But in case I'm wrong, please report the issue to the developers at: https://gitlab.gnome.org/GNOME/gnome-shell/issues They might have some more ideas. -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887914] Re: Partial freeze if booting with USB-C dock attached
I just realized this is the USB-C logic crashing in the kernel: Jul 21 20:31:20 volfe kernel: Call Trace: Jul 21 20:31:20 volfe kernel: ucsi_altmode_update_active+0xab/0xf0 [typec_ucsi] Jul 21 20:31:20 volfe kernel: ucsi_register_port+0x2c6/0x3c0 [typec_ucsi] Jul 21 20:31:20 volfe kernel: ucsi_init+0xd2/0x1c0 [typec_ucsi] Jul 21 20:31:20 volfe kernel: process_one_work+0x1eb/0x3b0 Jul 21 20:31:20 volfe kernel: worker_thread+0x4d/0x400 Jul 21 20:31:20 volfe kernel: kthread+0x104/0x140 Jul 21 20:31:20 volfe kernel: ? process_one_work+0x3b0/0x3b0 Jul 21 20:31:20 volfe kernel: ? kthread_park+0x90/0x90 Jul 21 20:31:20 volfe kernel: ret_from_fork+0x35/0x40 So it looks like a kernel bug. ** Package changed: mutter (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1887914 Title: Partial freeze if booting with USB-C dock attached Status in linux package in Ubuntu: New Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888065] Re: [nvidia] Screen dies/black after changing display orientation or enabling fractional scaling
That's odd because the fix for bug 1873403 isn't formally released to updates yet. But I'm glad your issue is gone. ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1888065 Title: [nvidia] Screen dies/black after changing display orientation or enabling fractional scaling Status in mutter package in Ubuntu: Fix Released Bug description: I upgraded to 20.04 over a month ago and it's been working fine. I have one monitor (external). I tried turning on fractional scaling in the display settings and the screen immediately turned black. I waited, expecting the "confirm changes" prompt to timeout and restore the display. It never did. Next I hard rebooted, but as soon as I'd entered my password to login, the screen went black again. Tried this a few more times. I then booted to a root console and `apt update/upgrade` to get all updates. Rebooting, I had the same issue on logging in. I then used Ctrl+Alt+F1 to get a virtual console, then back to F2, and a few other things. At some point I was able to log back in. Foolishly I assumed the issue was just with fractional scaling, and back in Display settings I for some reason decided to experiment further and flipped the display orientation to portrate. Immediately I got a black screen and ended back in the same reboot loop, always getting a black screen as soon as I tried to log back in. Searching online I couldn't seem to find a way to revert the display orientation. From another virtual console I was unable to run xrandr or start a wayland session to get to the settings panel. To do that I was trying to run: dbus-run-session -- gnome-shell --display-server --wayland But that's just something I found on the Web, I have no idea what I'm doing there. It just gave the error: (gnome-shell:) mutter-warning: **: Failed to open gpu 'dev/dri/card0 Failed to activate universal planes: Operation not permitted (gnome-shell:) mutter-warning: **: Failed to create backend: No GPUs found Eventually I found a suggestion on the Web to unplug the cable to the display, and after experimenting with that a bit and switching between virtual consoles, at some point it was logged in with a working display ... well, sort of. The colors and icons are weird like it's lost theming or something. Going into the Display settings it seems that the orientation has also been reset to landscape. I'm filing this bug before restarting the machine so I can report the system scan it has taken. At this point I've no idea whether I'll be able to log back in again after a reboot. I'll try that now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..21.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:21:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sat Jul 18 17:21:56 2020 DistUpgraded: 2020-04-29 16:04:33,258 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-37-generic, x86_64: installed nvidia, 435.21, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107GL [Quadro P400] [1028:11be] InstallationDate: Installed on 2019-11-03 (257 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Z4 G4 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=9586ebe6-be5f-4a32-b960-e129e9d98eb9 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-04-29 (80 days ago) dmi.bios.date: 03/21/2019 dmi.bios.vendor: HP dmi.bios.version: P62 v01.75 dmi.board.name: 81C5 dmi.board.vendor: HP dmi.board.version: MVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP62v01.75:bd03/21/2019:svnHP:pnHPZ4G4Workstation:pvr:rvnHP:rn81C5:rvrMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53335X HP
[Desktop-packages] [Bug 1879352] Re: /usr/bin/im-launch i3 fails
Please note that 'i3' is an argument to the command /usr/bin/im-launch, not part of a file name. So the error message incorrectly says "No such file or directory". It would still be good if you could try to install im-config: sudo apt purge im-config -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1879352 Title: /usr/bin/im-launch i3 fails Status in i3-wm package in Ubuntu: Expired Status in im-config package in Ubuntu: New Bug description: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1879352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879352] Re: /usr/bin/im-launch i3 fails
Sorry, s/install/uninstall/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1879352 Title: /usr/bin/im-launch i3 fails Status in i3-wm package in Ubuntu: Expired Status in im-config package in Ubuntu: New Bug description: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1879352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
The answer to your question is comment #15. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
[Desktop-packages] [Bug 1825679] Re: Delay/freeze/cpu spike when using the function/media/brightness keys in Xorg
Rafael, This bug is closed so the most helpful thing to do would be to open a new bug. Just run: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825679 Title: Delay/freeze/cpu spike when using the function/media/brightness keys in Xorg Status in gnome-shell package in Ubuntu: Expired Bug description: There is a long time bug when the user press any function key or media key om Gnome, the CPU spikes to 100%, the system freezes for some seconds and then the key is pressed. This is particularly true when change the screen brightness. This only happens in Xorg, Wayland is not affected. On Brazilian keyboard a workaround is to edit the file `/usr/share/X11/xkb/symbols/br` and comment the line `modifier_map Mod3 { Scroll_Lock };` This has been affecting multiple users and has been discussed on https://www.reddit.com/r/gnome/comments/84453o/delayfreezecpu_spike_when_using_the_functionmedia/ https://askubuntu.com/questions/1025302/media-keys-delayed-and-cause-a -cpu-spike-to-100-on-ubuntu-17-10-with-gnome https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on- ubuntu-gnome-17-04?noredirect=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880031] Re: Thumbnail is stretched if its aspect ratio is less than that of the container
This bug was fixed in the package gnome-shell-extension-desktop-icons - 20.04.0-3 --- gnome-shell-extension-desktop-icons (20.04.0-3) unstable; urgency=medium * d/p/Fix-incorrect-aspect-ratio.patch, d/p/desktopGrid.js-fix-errors-when-screen-size-changes.patch: - Fix incorrect icon aspect ratio (LP: #1880031) -- Marco Trevisan (Treviño) Tue, 21 Jul 2020 18:16:08 +0200 ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1880031 Title: Thumbnail is stretched if its aspect ratio is less than that of the container Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Bug description: This was discovered when investigating fix for bug #1868529. Aspect ratio is still not correct for images that are more narrow than the container. To reproduce, create an image that has aspect ratio, e.g., ~0.5 (e.g. width = 250 and height = 500). Line in fileItem.js where we calculate icon width does not count the margins (zero is used instead of actual margins): let containerWidth = Prefs.getDesiredWidth(scaleFactor, 0); Here is how the margins are being calculated in desktopGrid.js: this._extra_width = themeNode.get_margin(St.Side.LEFT) + themeNode.get_margin(St.Side.RIGHT) + themeNode.get_border_width(St.Side.LEFT) + themeNode.get_border_width(St.Side.RIGHT) + themeNode.get_horizontal_padding(); this._extra_height = themeNode.get_margin(St.Side.TOP) + themeNode.get_margin(St.Side.BOTTOM) + themeNode.get_border_width(St.Side.TOP) + themeNode.get_border_width(St.Side.BOTTOM) + themeNode.get_vertical_padding(); To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1880031/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825679] Re: Delay/freeze/cpu spike when using the function/media/brightness keys in Xorg
'apport-collect 1825679' won't work because I'm not the author or because the report is closed. I'm attaching the journalctl output. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825679/+attachment/5394752/+files/journalctl.log -- 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/1825679 Title: Delay/freeze/cpu spike when using the function/media/brightness keys in Xorg Status in gnome-shell package in Ubuntu: Expired Bug description: There is a long time bug when the user press any function key or media key om Gnome, the CPU spikes to 100%, the system freezes for some seconds and then the key is pressed. This is particularly true when change the screen brightness. This only happens in Xorg, Wayland is not affected. On Brazilian keyboard a workaround is to edit the file `/usr/share/X11/xkb/symbols/br` and comment the line `modifier_map Mod3 { Scroll_Lock };` This has been affecting multiple users and has been discussed on https://www.reddit.com/r/gnome/comments/84453o/delayfreezecpu_spike_when_using_the_functionmedia/ https://askubuntu.com/questions/1025302/media-keys-delayed-and-cause-a -cpu-spike-to-100-on-ubuntu-17-10-with-gnome https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on- ubuntu-gnome-17-04?noredirect=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
A workaround, if you really need auto-login, is to install lightdm (at this point still choose gdm3), enable auto-login via gnome settings, then switch to lightdm (sudo dpkg-reconfigure gdm3). Not sure why it autologins but it does. Can't lock the gnome session however as not using gdm anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 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 PPA:
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
What's the status for Ubuntu Focal? How can I help to emphasize the importance of backporting the fix to the stable release? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1885744] Re: HIde im-config in application menus/searches
I verified the test case using im-config 0.44-1ubuntu1.1 from focal- proposed. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1885744 Title: HIde im-config in application menus/searches Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Focal: Fix Committed Bug description: [Impact] I'm refering to this conversation: https://discourse.ubuntu.com/t/improve-presentation-of-input-method-as-search-result-in-all-applications/17031/2 Current situation: === - Settings of im-config can be accomplished by "Language Support" ( see https://ubuntucommunity.s3.dualstack.us-east-2.amazonaws.com/original/2X/4/43cc792173e336454a8d38e3c35b950fbfb48975.png ) - im-config is difficult to understand for "normal users" Suggestion: === Hide im-config from application menu / searches [Test Case] * Open Activities and find that "Input Method" is found * Install im-config from focal-proposed * Open Activities and find that "Input Method" is no longer found [Regression Potential] Minimal; only a tiny change in the .desktop file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1885744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
It also happens with driver nvidia-340.108 in elementary OS 5.1.6 Hera. In my case the error happens with VLC when trying to open the Hikvision rstp streaming (H264), the error lines run fast but stop when closing VLC. I leave some lines of the error. VLC media player 3.0.11 Vetinari (revision 3.0.11-0-gdc0c5ced72) [564386f97a00] main libvlc: Ejecutar vlc con la interfaz predeterminada. Use «cvlc» para usar vlc sin interfaz. Qt: Session management error: None of the authentication protocols specified are supported QApplication: invalid style override 'adwaita' passed, ignoring it. Available styles: Breeze, Windows, Fusion [564386f8d3c0] main playlist: playlist is empty [7fc12c04aee0] main decoder error: buffer deadlock prevented MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (25). 70154 bytes of trailing data will be dropped! MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (50). 100677 bytes of trailing data will be dropped! [h264 @ 0x7fc13000a4e0] illegal memory management control operation 13 [7fc1340020b0] egl_x11 gl error: cannot select OpenGL API [7fc12c04aee0] avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 340.108 Wed Dec 11 14:31:24 PST 2019 for hardware decoding [h264 @ 0x7fc13000a4e0] Failed setup for format vdpau: hwaccel initialisation returned error. [7fc12c04aee0] avcodec decoder error: existing hardware acceleration cannot be reused [h264 @ 0x7fc13000a4e0] top block unavailable for requested intra mode -1 [h264 @ 0x7fc13000a4e0] error while decoding MB 2 0, bytestream 668 [h264 @ 0x7fc130026900] Missing reference picture, default is 65530 [h264 @ 0x7fc130026900] Missing reference picture, default is 65530 [h264 @ 0x7fc13002dec0] Missing reference picture, default is 65526 [h264 @ 0x7fc13002dec0] Missing reference picture, default is 65526 [h264 @ 0x7fc13008ab20] Missing reference picture, default is 65528 [h264 @ 0x7fc13008ab20] Missing reference picture, default is 65528 [h264 @ 0x7fc1300a6aa0] cabac_init_idc 3 overflow [h264 @ 0x7fc1300a6aa0] decode_slice_header error [h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65530 [h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65530 [h264 @ 0x7fc13000a4e0] illegal modification_of_pic_nums_idc 6 [h264 @ 0x7fc13000a4e0] decode_slice_header error [h264 @ 0x7fc130026900] Missing reference picture, default is 65531 [h264 @ 0x7fc130026900] Missing reference picture, default is 65531 [h264 @ 0x7fc13002dec0] Missing reference picture, default is 65532 [h264 @ 0x7fc13002dec0] Missing reference picture, default is 65532 [h264 @ 0x7fc13008ab20] Missing reference picture, default is 65534 [h264 @ 0x7fc13008ab20] Missing reference picture, default is 65534 [h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65536 [h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65536 [h264 @ 0x7fc13000a4e0] cabac_init_idc 3 overflow [h264 @ 0x7fc13000a4e0] decode_slice_header error [7fc138078d00] freetype spu text error: LayoutParagraph(): Invalid max width [7fc138078d00] freetype spu text error: LayoutParagraph(): Invalid max width [h264 @ 0x7fc13000a4e0] Missing reference picture, default is 65538 [h264 @ 0x7fc13000a4e0] Missing reference picture, default is 65538 [h264 @ 0x7fc130026900] reference count overflow [h264 @ 0x7fc130026900] decode_slice_header error -- 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/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video
[Desktop-packages] [Bug 1885610] Re: enlarged components on lock/login screen
Hello, sorry to be getting back to you so late. I just tried your previous suggestions and the bug still persists. Also, in my previous screenshot the top panel was displaying according to the default theme setting. -- 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/1885610 Title: enlarged components on lock/login screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Source Package: usr/bin/gnome-shell Ubuntu Release: 20.04 LTS Package Version: 3.36.2-1ubuntu1~20.04.1 Expected: Normal sized components on lock/login screen Happened: Enlarged components on lock/login screen This behavior is unaffected by resolution size from different monitors ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Flat-Remix-Miami-Dark-GNOME:GNOME Date: Mon Jun 29 13:01:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-02 (331 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 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-06-27 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1885610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
And the cashier side ** Attachment added: "Cashier side of the setup" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394700/+files/Bug1888098_opposingScreensCashier.jpeg -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
And before anyone starts anything about freeloading. I donate several thousand euros per year and a lot of my time to open source projects. So, let's not go there. Once again thank you. I hope that it's much clearer now what is not working as expected in Ubuntu 20.04's iteration of Gnome Desktop. -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
So you can see what the system looks like when installed ** Attachment added: "Opposing Screens Customer" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394699/+files/Bug1888098_opposingScreensCashier.jpeg -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
This bug was fixed in the package linux-oem - 4.15.0-1093.103 --- linux-oem (4.15.0-1093.103) bionic; urgency=medium * bionic/linux-oem: 4.15.0-1093.103 -proposed tracker (LP: #1887026) * [SRU] plug headset won't proper reconfig ouput to it on machine with default output (LP: #1882248) - SAUCE: ALSA: hda - let hs_mic be picked ahead of hp_mic * Freezing on boot since kernel 4.15.0-72-generic release (LP: #1856387) - x86/timer: Don't skip PIT setup when APIC is disabled or in legacy mode [ Ubuntu: 4.15.0-112.113 ] * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2020-11935 - SAUCE: aufs: do not call i_readcount_inc() - SAUCE: aufs: bugfix, IMA i_readcount * CVE-2020-10757 - mm: Fix mremap not considering huge pmd devmap * Update lockdown patches (LP: #1884159) - efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN - efi: Restrict efivar_ssdt_load when the kernel is locked down - powerpc/xmon: add read-only mode - powerpc/xmon: Restrict when kernel is locked down - [Config] CONFIG_XMON_DEFAULT_RO_MODE=y - SAUCE: acpi: disallow loading configfs acpi tables when locked down * seccomp_bpf fails on powerpc (LP: #1885757) - SAUCE: selftests/seccomp: fix ptrace tests on powerpc * Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers (LP: #1881137) - [packaging] add signed modules for the 418-server and the 440-server flavours [ Ubuntu: 4.15.0-111.112 ] * bionic/linux: 4.15.0-111.112 -proposed tracker (LP: #1886999) * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - SAUCE: mlxsw: Add missmerged ERR_PTR hunk * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668) - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" -- Kelsey Skunberg Tue, 14 Jul 2020 12:21:34 -0600 ** Changed in: linux-oem (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935 -- 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/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Some more fun, the onscreen keyboard follows the misplaced dialog box to the non-touchable monitor. ** Attachment added: "Screen Keyboard opens on non touchable area" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394696/+files/Bug1888098_ScreenKeyboardOnNonTouchMonitor.jpeg -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886565] Re: SRU the current 3.36.7 stable update
Hello Sebastien, or anyone else affected, Accepted evince into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evince/3.36.7-0ubuntu1 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: evince (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1886565 Title: SRU the current 3.36.7 stable update Status in evince package in Ubuntu: Fix Released Status in evince source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evince/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Open some pdf and ps documents, check that they render properly * Regression potential There is no specific change or feature to test in this update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1886565/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
And here is proof that there are no extensions enabled ** Attachment added: "No Extensions enabled" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394697/+files/Bug1888098_ProofAllExtensionsDisabled.jpeg -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Here is an extra treat so you can see why block Caribou is very necessary and the gnome onscreen keyboard implementation makes the system completely unusable. ** Attachment added: "Extra treat why the block caribou extension was on." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394695/+files/Bug1888098_whyGnomeKeyboardIsOff.jpeg -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Here is a photo so you can see that the Center New Window option does nothing. At least it stopped doing the Easter Egg of putting things halfway between two monitors that's a plus. :D ** Attachment added: "Photo Center new window doesn't do anything" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394694/+files/Bug1888098_CenterNewWindowIgnored.jpeg -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888425] [NEW] Ubuntu Freezy - Probably Gnome-Shell Bug
Public bug reported: I have got a Ryzen 7 2700X, Nvidia GTX 1080 Ti and 16 GB RAM. Ubuntu sometimes freezes and I can't do nothing. I need to reboot the system pressing reset button. Usually Ubuntu (I think that Gnome-shell) freezes when I am selecting a game in Steam. When I select one game and change to another selecting the other, Ubuntu freezes. But it doesn't happen always. I read that could be a problem with Ryzen CPUs, but I don't know. Sorry and thanks for your time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 21 22:11:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (87 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.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) ** Affects: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888425 Title: Ubuntu Freezy - Probably Gnome-Shell Bug Status in gnome-shell package in Ubuntu: New Bug description: I have got a Ryzen 7 2700X, Nvidia GTX 1080 Ti and 16 GB RAM. Ubuntu sometimes freezes and I can't do nothing. I need to reboot the system pressing reset button. Usually Ubuntu (I think that Gnome-shell) freezes when I am selecting a game in Steam. When I select one game and change to another selecting the other, Ubuntu freezes. But it doesn't happen always. I read that could be a problem with Ryzen CPUs, but I don't know. Sorry and thanks for your time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 21 22:11:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (87 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.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/1888425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_s
Hello errors.ubuntu.com, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1857947 Title: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from call_later_func() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes [ Test case ] Four-finger gesture seems to trigger it, in any case it can be monitored via - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1+git20191024-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1857947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
Hello Ivan, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870867 Title: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl)) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes in meta_x11_get_stage_window. [ Test case ] Perform touch events via touchpad or touchscreen, eventually the shell will crash. Errors can be monitored at: https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). --- ProblemType: CrashDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 22:08:06 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago) UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist across reboots in resizable VM windows
Hello Niels, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1884754 Title: Fractional scaling does not persist across reboots in resizable VM windows Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. [ Test case ] Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - After next reboot the setting is reverted to 100%, but should use previous value [ Regression potential ] Resolution doesn't adapt properly to the vmware player window size. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: 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/1884754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it
Hello Marco, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1887998 Title: Update to 3.36.4 and SRU it Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 screencasting and touch-interaction, so ensure there are no problems with those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886996] Re: Restore previous configuration after turning off fractional scaling does not work
Hello Marco, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1886996 Title: Restore previous configuration after turning off fractional scaling does not work Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] It's not possible to restore the application a non-fractional scaling configuration when fractional scaling was previously enabled and applied. [ Test case ] 1. From control center, display panel, enable fractional scaling 2. Set scaling to some fractional value and apply and confirm it. 3. Turn off the fractional scaling switch and apply it 4. Fractional scaling should be reverted to the selected integer scaling. 5. When gnome-shell shows the confirmation dialog, click "Revert Settings" 6. Expect the fractional scaling to be re-enabled and applied as it used to be [ Regression potential ] - Configuration can't be applied - Scaling (fractional or not) is not properly applied in single and multi-monitor - Fractional scaling can't be toggled anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1886996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873298] Re: No way to enroll multiple fingers for identification
Tried with fprintd-list (both listed), fprintd-verify (only first matching) and deleting/new assigning (same result) with my closed source goodix 530c. I guess it's a driver-bug...not gnome-control-center one. Sorry for the noise -- 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/1873298 Title: No way to enroll multiple fingers for identification Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Bug description: * Impact This is the continuation of bug #1865845. In g-c-c user panel, it is not possible to enroll more than one finger for authentication. * Test Case 1. enroll fingerprint in gnome-control-center 2. close the dialog 3. click it again to enroll another finger 4. it shows a dialog requiring you to delete your fingerprints * Impact As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 There will be few new strings, although most of the action events are already covered by the fprintd translations. UI will change quite a lot, but the current documentation [1] should not be affected by the change, being quite generic, but in case it might be updated to be clearer. The change are important improvements and oem request so believe it's right to carry over as a SRU and considered as hardware enablement The new strings are already translatable on launchpad and the translators mailing list has been notified, hopefully we can get some coverage for the new UI in time for the LTS .1 langpack refresh [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Hello Matt, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Thanks for have a new look at this Oh and I forgot to mention this is with the option Center New Windows turned ON in Gnome Tweak Tool Which should theoretically do the same as the DCONF edit line, right? -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
Hello Daniel, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers source package in Focal: Confirmed Bug description: [ Impact ] When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 [ Test case ] In a Nvidia system: - From g-c-c enable fractional scaling - Set all the available fractional scaling values and ensure they work + In any case the screen should be turned off [ Regression potential ] Wrong screen size is set and panning might be enabled. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876894] Re: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling
Hello Iain, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Focal) Status: New => Fix Committed ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1876894 Title: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling Status in gnome-control-center package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: * Impact Scaling is not reverted properly (appears shrunk) when disabling fractional scaling * Test Case Do this in an Ubuntu/Xorg session: 0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 100% 1. Open gnome-control-center → displays 2. Turn on fractional scaling 3. Select 125% 4. Press apply (the scaling should correctly change now) 5. Turn off fractional scaling by changing the toggle Now everything is shrunk - it's not been returned to 100% properly. See the attached screenshot where the text is tiny instead of regular 100% size. If you do this instead of step 5: 5. Select 100% scaling 7. Press apply 8. Turn off fractional scaling by changing the toggle Then everything returns to the normal size. Repeat the same selecting 200% at 5., (or 100% if 200% was your default) and ensure it's applied. I'm on nvidia(-440), but Séb said that he saw this on his Intel machine too. * Regression potential Verify that scaling changes are correctly applied on different setup ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 10:57:40 2020 InstallationDate: Installed on 2012-10-07 (2766 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Here is a photo so it's easier to understand what the issue is. ** Attachment added: "Photo of the issue faced" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394688/+files/2020-07-21_Bug%20-1888098_GnomeWindowPlacementBug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Removing the extensions has the same effect. Block Caribou 36 is necessary as the Point of Sale system (Open source) already has all the buttons and keyboard that are necessary for the use of the Point of Sale system. Yet it contains text entry fields which pop up the on-screen keyboard. There are more touchscreen applications that tablets, such as Kiosks and Point of Sale systems. "gsettings set org.gnome.mutter center-new-windows true" is an easter- egg joke, it puts the windows halfway between the two screens, then stacks them on top of each other. "I think this is probably occurring because the primary display is occupied by a window already. So any more new windows go to the next display that has empty space. If that's true then this is not a bug. And hopefully #3 is good enough." This is a serious bug as the screens are opposing one another. There are two different people with two different information goals looking at each screen. Both screens are occupied by full screen windows. One is the point of sale interface for the cashier and the other is the customer display screen showing the products the customer is purchasing. The expected behavior is to put the window on the same monitor to where the button to open the new window has been pressed. I'll see if I can muster up some screenshots to make it more visual as to what is going on. -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.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/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887914] Re: Partial freeze if booting with USB-C dock attached
Sure thing, thanks for following up! Attached is the log of the boot leading to a freeze. I did delete some log lines for privacy (NetworkManager output, mostly). ** Attachment added: "Output of journalctl -b-1 (some lines deleted for privacy reasons)." https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887914/+attachment/5394675/+files/prevboot.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in mutter package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887914] Re: Partial freeze if booting with USB-C dock attached
** Attachment added: "Output of lspci -k" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887914/+attachment/5394674/+files/lspcik.txt -- 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/1887914 Title: Partial freeze if booting with USB-C dock attached Status in mutter package in Ubuntu: Incomplete Bug description: When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a kind of dock) already attached, the machine crashes after entering password into the graphical login interface. More precisely the login does not complete (in a reasonable time frame) and I cannot switch to another virtual terminal. Some menus can be selected, but there is no action (e.g. reboot) and I have to do a hard shutdown (pressing the power button for 4 sec.). The log files show a kernel oops. When attaching the dock after login the system seems to work normally. I do have the latest displaylink drivers installed (www.displaylink.com). Attached is a log file snippet. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-03-25 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: mutter 3.36.3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878285] Re: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050
Hello Thovi, or anyone else affected, Accepted libfprint into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libfprint/1:1.90.2+tod1-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- 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/1878285 Title: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050 Status in libfprint: Unknown Status in gnome-control-center package in Ubuntu: Won't Fix Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: Fix Committed Bug description: [ Impact ] When I try to setup my fingerprint in gnome-control-center, I first have to choose which finger I would use, and when I press the "next" button, it crashes : "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying". For information, my fingerprint sensor is : - lsusb Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint Sensor [ Test case ] With a fingerprint reader 138a:0050: - Open gnome-control-center user-accounts - Select the fingeprint row to enroll a finger - Follow the procedure and the finger should be enrolled - Verify with: fprintd-list $USER [ Regression potential ] - The fingerprint is not read by the sensor --- Ubuntu 20.04 gnome-control-center: Installé : 1:3.36.1-1ubuntu5 Candidat : 1:3.36.1-1ubuntu5 Table de version : *** 1:3.36.1-1ubuntu5 500 500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen, is that everything works and that I can set up my finger for unlocking. What happened instead : it crashes with the information "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying". ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 22:00:30 2020 InstallationDate: Installed on 2020-05-11 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=fr_BE:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bashSourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1878285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873298] Re: No way to enroll multiple fingers for identification
tested the package, gui-bug seems to be fixed, i can add fingerprints and delete them. but it looks like they are not registered the right way...i can only login with the first finger i added (tried also reboot and second is still listed in gnome-control-center)the other one added with the new gui is not recognized...can i check if the fingerprints are added right? unlock seems to need additional Patch from gnome-shell (gnome-flashback session) strange is that the dialog is not movable (titlebar-dragging), is this intented? -- 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/1873298 Title: No way to enroll multiple fingers for identification Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Bug description: * Impact This is the continuation of bug #1865845. In g-c-c user panel, it is not possible to enroll more than one finger for authentication. * Test Case 1. enroll fingerprint in gnome-control-center 2. close the dialog 3. click it again to enroll another finger 4. it shows a dialog requiring you to delete your fingerprints * Impact As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 There will be few new strings, although most of the action events are already covered by the fprintd translations. UI will change quite a lot, but the current documentation [1] should not be affected by the change, being quite generic, but in case it might be updated to be clearer. The change are important improvements and oem request so believe it's right to carry over as a SRU and considered as hardware enablement The new strings are already translatable on launchpad and the translators mailing list has been notified, hopefully we can get some coverage for the new UI in time for the LTS .1 langpack refresh [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351] Re: Have option to not automatically open next email
** Changed in: thunderbird Status: Confirmed => Invalid -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Invalid Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351]
(In reply to R. Diez from comment #71) > I wanted to mention that other users like me would like to see this annoying > behaviour fixed. Seconded -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Invalid Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351]
Thanks for the add-on so far. I'm continuing to use it with Thunderbird 60 for an indeterminate time to come. Newer versions of Thunderbird broke too many things and took away too many features I regularly use, so that's not for me anymore. -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Invalid Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351]
I wanted to mention that other users like me would like to see this annoying behaviour fixed. -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Invalid Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351]
This feature has been implemented in the new (v78) Select Messages column; unchecking it will permanently prevent any auto selection in the folder. It is pretty much this patch, except the reviewers in Bug 1017904 didn't not get it. Note that using ctrl-click to unselect will continue to NOT work, the message must be unselected in the column checkbox. -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Invalid Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351]
Just a small update: my add-on mentioned in comment 37 no longer works due to the changes in the add-ons API. Sadly, I don't have time to fix this since I already have too many things on my plate. This means that there's not really any existing solution for this bug for TB 78 users. Some sort of fix along the lines of the attached patch (i.e. something that doesn't require setting a pref) would probably be ideal, although I haven't done much Thunderbird stuff for a while so couldn't say exactly what the behavior should be... -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Invalid Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's
The warning you are copying are not related to your connectivity issue, but the problem you describe seems rather one with wpasupplicant or with the driver, I'm reassigning to the kernel ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- 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/1888390 Title: apparmor error causing deauthentication for certain SSID's Status in linux package in Ubuntu: New Bug description: dmesg output: [ 83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/UDisks2" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name=":1.4" pid=1922 label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [ 165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80 [ 165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3) [ 165.568883] wlan0: authenticated [ 165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3) [ 165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 status=0 aid=3) [ 165.579888] wlan0: associated [ 165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice (Reason: 3=DEAUTH_LEAVING) Release Information: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic Expected outcome: Connecting to the home network Actual outcome: deauthentication by local choice (Reason:3=DEAUTH_LEAVING) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886480] Update Released
The verification of the Stable Release Update for eog has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1886480 Title: SRU the current 3.36.3 stable update Status in eog package in Ubuntu: Fix Released Status in eog source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/eog/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Try opening images on different format, browse directories and do simple transformations like rotations. * Regression potential There is no specific change to test there, the update has some fixes around keybinding, check that those work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1886480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886480] Re: SRU the current 3.36.3 stable update
This bug was fixed in the package eog - 3.36.3-0ubuntu1 --- eog (3.36.3-0ubuntu1) focal; urgency=medium * New stable version (lp: #1886480) -- Sebastien Bacher Mon, 06 Jul 2020 16:17:23 +0200 ** Changed in: eog (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1886480 Title: SRU the current 3.36.3 stable update Status in eog package in Ubuntu: Fix Released Status in eog source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/eog/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Try opening images on different format, browse directories and do simple transformations like rotations. * Regression potential There is no specific change to test there, the update has some fixes around keybinding, check that those work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1886480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's
audit: type=1107 audit(1595014020.261:196): pid=1051 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager/ActiveConnection/4" interface="org.freedesktop.NetworkManager.Connection.Active" member="PropertiesChanged" name=":1.12" mask="receive" pid=2401 label="snap.telegram-desktop.telegram-desktop" peer_pid=1057 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [ 477.870889] audit: type=1107 audit(1595014065.447:197): pid=1051 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="PropertiesChanged" name=":1.12" mask="receive" pid=2401 label="snap.telegram-desktop.telegram-desktop" peer_pid=1057 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [ 477.870985] audit: type=1107 audit(1595014065.447:198): pid=1051 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager/ActiveConnection/4" interface="org.freedesktop.NetworkManager.Connection.Active" member="PropertiesChanged" name=":1.12" mask="receive" pid=2401 label="snap.telegram-desktop.telegram-desktop" peer_pid=1057 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [ 477.871464] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice (Reason: 3=DEAUTH_LEAVING) this was the output from dmesg previously before I, along with family members who are more versed in tech in general, attempted to fix the issue, which sadly did not bring results at my home. The behaviour I expected was that my laptop will connect to the home network (already known network) as per usual. What I encountered was/is that whenever I attempt to connect to the network, the ssid is recognized, it briefly attempts to connect before deauthenticating by local choice (Reason:3=DEAUTH_LEAVING). I have done nothing to cause this to occur. I have done almost everything I can, excluding resetting the settings of the home network -- 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/1888390 Title: apparmor error causing deauthentication for certain SSID's Status in network-manager package in Ubuntu: Incomplete Bug description: dmesg output: [ 83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/UDisks2" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name=":1.4" pid=1922 label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [ 165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80 [ 165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3) [ 165.568883] wlan0: authenticated [ 165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3) [ 165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 status=0 aid=3) [ 165.579888] wlan0: associated [ 165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice (Reason: 3=DEAUTH_LEAVING) Release Information: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic Expected outcome: Connecting to the home network Actual outcome: deauthentication by local choice (Reason:3=DEAUTH_LEAVING) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1888390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist across reboots in resizable VM windows
** Changed in: mutter (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1884754 Title: Fractional scaling does not persist across reboots in resizable VM windows Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. [ Test case ] Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - After next reboot the setting is reverted to 100%, but should use previous value [ Regression potential ] Resolution doesn't adapt properly to the vmware player window size. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: 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/1884754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
** Changed in: mutter (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Desktop-packages] [Bug 1882271] Re: adwaita-icon-theme is missing window action icons
** Changed in: adwaita-icon-theme (Ubuntu Focal) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adwaita-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1882271 Title: adwaita-icon-theme is missing window action icons Status in adwaita-icon-theme package in Ubuntu: Fix Committed Status in adwaita-icon-theme source package in Focal: Won't Fix Bug description: [ Impact ] Various window-* operation icons are missing in the adwaita-icon-theme (but available in the full one) even if they're fundamental for gtk apps. In focal the icons are: dpkg -L adwaita-icon-theme | grep "window-.*" /usr/share/icons/Adwaita/scalable/ui/window-close-symbolic.svg /usr/share/icons/Adwaita/scalable/ui/window-maximize-symbolic.svg /usr/share/icons/Adwaita/scalable/ui/window-minimize-symbolic.svg /usr/share/icons/Adwaita/scalable/ui/window-new-symbolic.svg /usr/share/icons/Adwaita/scalable/ui/window-restore-symbolic.svg [ Test case ] dpkg -L adwaita-icon-theme | grep "window-.*" It should contain /usr/share/icons/Adwaita/16x16/legacy/window-close.png /usr/share/icons/Adwaita/16x16/legacy/window-new.png /usr/share/icons/Adwaita/16x16/ui/window-close-symbolic.symbolic.png /usr/share/icons/Adwaita/16x16/ui/window-maximize-symbolic.symbolic.png /usr/share/icons/Adwaita/16x16/ui/window-minimize-symbolic.symbolic.png /usr/share/icons/Adwaita/16x16/ui/window-new-symbolic.symbolic.png /usr/share/icons/Adwaita/16x16/ui/window-restore-symbolic.symbolic.png /usr/share/icons/Adwaita/22x22/legacy/window-close.png /usr/share/icons/Adwaita/22x22/legacy/window-new.png /usr/share/icons/Adwaita/24x24/legacy/window-close.png /usr/share/icons/Adwaita/24x24/legacy/window-new.png /usr/share/icons/Adwaita/24x24/ui/window-close-symbolic.symbolic.png /usr/share/icons/Adwaita/24x24/ui/window-maximize-symbolic.symbolic.png /usr/share/icons/Adwaita/24x24/ui/window-minimize-symbolic.symbolic.png /usr/share/icons/Adwaita/24x24/ui/window-new-symbolic.symbolic.png /usr/share/icons/Adwaita/24x24/ui/window-restore-symbolic.symbolic.png /usr/share/icons/Adwaita/32x32/legacy/window-close.png /usr/share/icons/Adwaita/32x32/legacy/window-new.png /usr/share/icons/Adwaita/32x32/ui/window-close-symbolic.symbolic.png /usr/share/icons/Adwaita/32x32/ui/window-maximize-symbolic.symbolic.png /usr/share/icons/Adwaita/32x32/ui/window-minimize-symbolic.symbolic.png /usr/share/icons/Adwaita/32x32/ui/window-new-symbolic.symbolic.png /usr/share/icons/Adwaita/32x32/ui/window-restore-symbolic.symbolic.png /usr/share/icons/Adwaita/48x48/legacy/window-close.png /usr/share/icons/Adwaita/48x48/legacy/window-new.png /usr/share/icons/Adwaita/48x48/ui/window-close-symbolic.symbolic.png /usr/share/icons/Adwaita/48x48/ui/window-maximize-symbolic.symbolic.png /usr/share/icons/Adwaita/48x48/ui/window-minimize-symbolic.symbolic.png /usr/share/icons/Adwaita/48x48/ui/window-new-symbolic.symbolic.png /usr/share/icons/Adwaita/48x48/ui/window-restore-symbolic.symbolic.png /usr/share/icons/Adwaita/64x64/ui/window-close-symbolic.symbolic.png /usr/share/icons/Adwaita/64x64/ui/window-maximize-symbolic.symbolic.png /usr/share/icons/Adwaita/64x64/ui/window-minimize-symbolic.symbolic.png /usr/share/icons/Adwaita/64x64/ui/window-new-symbolic.symbolic.png /usr/share/icons/Adwaita/64x64/ui/window-restore-symbolic.symbolic.png /usr/share/icons/Adwaita/96x96/ui/window-close-symbolic.symbolic.png /usr/share/icons/Adwaita/96x96/ui/window-maximize-symbolic.symbolic.png /usr/share/icons/Adwaita/96x96/ui/window-minimize-symbolic.symbolic.png /usr/share/icons/Adwaita/96x96/ui/window-new-symbolic.symbolic.png /usr/share/icons/Adwaita/96x96/ui/window-restore-symbolic.symbolic.png /usr/share/icons/Adwaita/scalable/ui/window-close-symbolic.svg /usr/share/icons/Adwaita/scalable/ui/window-maximize-symbolic.svg /usr/share/icons/Adwaita/scalable/ui/window-minimize-symbolic.svg /usr/share/icons/Adwaita/scalable/ui/window-new-symbolic.svg /usr/share/icons/Adwaita/scalable/ui/window-restore-symbolic.svg [ Regression potential ] Fixed-size icons may be chosen in some cases, leading some slight quality loss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1882271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it
** Changed in: mutter (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1887998 Title: Update to 3.36.4 and SRU it Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 screencasting and touch-interaction, so ensure there are no problems with those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1888390 Title: apparmor error causing deauthentication for certain SSID's Status in network-manager package in Ubuntu: Incomplete Bug description: dmesg output: [ 83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/UDisks2" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name=":1.4" pid=1922 label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [ 165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80 [ 165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3) [ 165.568883] wlan0: authenticated [ 165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3) [ 165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 status=0 aid=3) [ 165.579888] wlan0: associated [ 165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice (Reason: 3=DEAUTH_LEAVING) Release Information: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic Expected outcome: Connecting to the home network Actual outcome: deauthentication by local choice (Reason:3=DEAUTH_LEAVING) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1888390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's
the warning you shared indicates that a snap called indicator-sensors tries to talking to udisks without having the proper permission, that's not sign of an authentification issue... -- 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/1888390 Title: apparmor error causing deauthentication for certain SSID's Status in network-manager package in Ubuntu: Incomplete Bug description: dmesg output: [ 83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/UDisks2" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name=":1.4" pid=1922 label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [ 165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80 [ 165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3) [ 165.568883] wlan0: authenticated [ 165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3) [ 165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 status=0 aid=3) [ 165.579888] wlan0: associated [ 165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice (Reason: 3=DEAUTH_LEAVING) Release Information: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic Expected outcome: Connecting to the home network Actual outcome: deauthentication by local choice (Reason:3=DEAUTH_LEAVING) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1888390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881482] Re: adding fingerprints not possible
*** This bug is a duplicate of bug 1873298 *** https://bugs.launchpad.net/bugs/1873298 ** This bug has been marked a duplicate of bug 1873298 No way to enroll multiple fingers for identification -- 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/1881482 Title: adding fingerprints not possible Status in gnome-control-center package in Ubuntu: New Bug description: hi, after getting my fingerprint-reader working, i wonder why i can only define 1 fungerprint in gnome-settings dialog (system->users->fingerprint login add finger). i have defined one, fingerprint-usage is activated, if i click on the setting i will be asked about deleting the fingerprints to disable. here i can delete or cancel...as i do not want to delete i click cancel and expect the dialog for adding additional fingers...but this does not happen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Sun May 31 16:20:32 2020 InstallationDate: Installed on 2020-04-27 (34 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: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1881482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881482] Re: adding fingerprints not possible
is issue clear enough? can i manually open the dialog for adding fingerprints (e.g. from terminal)? -- 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/1881482 Title: adding fingerprints not possible Status in gnome-control-center package in Ubuntu: New Bug description: hi, after getting my fingerprint-reader working, i wonder why i can only define 1 fungerprint in gnome-settings dialog (system->users->fingerprint login add finger). i have defined one, fingerprint-usage is activated, if i click on the setting i will be asked about deleting the fingerprints to disable. here i can delete or cancel...as i do not want to delete i click cancel and expect the dialog for adding additional fingers...but this does not happen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Sun May 31 16:20:32 2020 InstallationDate: Installed on 2020-04-27 (34 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: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1881482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825679] Re: Delay/freeze/cpu spike when using the function/media/brightness keys in Xorg
Rafael, Can you please do as Sebastien suggested? I can't help as I don't have this machine anymore. -- 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/1825679 Title: Delay/freeze/cpu spike when using the function/media/brightness keys in Xorg Status in gnome-shell package in Ubuntu: Expired Bug description: There is a long time bug when the user press any function key or media key om Gnome, the CPU spikes to 100%, the system freezes for some seconds and then the key is pressed. This is particularly true when change the screen brightness. This only happens in Xorg, Wayland is not affected. On Brazilian keyboard a workaround is to edit the file `/usr/share/X11/xkb/symbols/br` and comment the line `modifier_map Mod3 { Scroll_Lock };` This has been affecting multiple users and has been discussed on https://www.reddit.com/r/gnome/comments/84453o/delayfreezecpu_spike_when_using_the_functionmedia/ https://askubuntu.com/questions/1025302/media-keys-delayed-and-cause-a -cpu-spike-to-100-on-ubuntu-17-10-with-gnome https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on- ubuntu-gnome-17-04?noredirect=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Has anyone built this package for 20.04 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21 10:57:26 pc kernel: [ 9475.309388] do_syscall_64+0x57/0x190 Oct 21 10:57:26 pc kernel: [ 9475.309392] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00
[Desktop-packages] [Bug 1866999] Re: gnome-calendar does not sync with Google Calendar
Same issue here. I can't see any new or updated events in calendar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879333] Re: [nvidia] Black screen on loading latest system update
Occurred again today after the kernel update was installed and system reset. When is this issue going to get fixed! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1879333 Title: [nvidia] Black screen on loading latest system update Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: This bug has been around since 16.04 and still occurs with 18.04 when using nvidia drivers. When update required for the OS the black screen situation happens after the required reboot. Only way to regain desktop is to login via ssh terminal and run the commands listed here: https://askubuntu.com/questions/1129516/black-screen-at-boot-after- nvidia-driver-installation-on-ubuntu-18-04-2-lts sudo apt-get update sudo apt-get upgrade sudo apt-get purge nvidia* sudo apt autoremove sudo apt-get install dkms build-essential linux-headers-$(uname -r) echo "# Disable the default Nouveau kernel driver" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf echo "# -" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf echo "blacklist nouveau" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "blacklist lbm-nouveau" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d /blacklist-nouveau.conf echo "alias nouveau off" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "alias lbm-nouveau off" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf cat /etc/modprobe.d/blacklist-nouveau.conf echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d /nouveau-kms.conf cat /etc/modprobe.d/nouveau-kms.conf sudo update-initramfs -u sudo service lightdm stop sudo apt-get install nvidia-driver-440 lsmod | grep nvidia sudo lshw -c video | grep 'configuration' sudo reboot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon May 18 08:44:05 2020 DistUpgraded: 2019-12-17 11:35:32,743 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-101-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. bbswitch, 0.8, 4.15.0-99-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1849:22b1] NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] [10de:1284] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 630 Rev. 2] [1043:846a] InstallationDate: Installed on 2019-09-26 (234 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. 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.15.0-101-generic root=UUID=89ea4739-64a1-4200-9626-c597e9d5a485 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2019-12-17 (152 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: N3150M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd02/27/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150M:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1883819] Re: Update to 3.36.3
Hello Robert, or anyone else affected, Accepted simple-scan into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/simple- scan/3.36.3-0ubuntu0.20.04.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1883819 Title: Update to 3.36.3 Status in simple-scan package in Ubuntu: New Status in simple-scan source package in Focal: Fix Committed Bug description: [ Description ] GNOME upstream have released a new stable version of simple-scan. Overview of changes in simple-scan 3.36.3 * Change the size of the paper to avoid visual glitches. * Disable possibility of scanning if no device is found, to avoid unnecessary errors. Overview of changes in simple-scan 3.36.2.1 * Revert the higher bit depth text scans changes - they aren't working with PDF saving. Overview of changes in simple-scan 3.36.2 * Use higher bit depth on text scans. * Fix size of first page on second scan. * Don't interrupt scanning if the device is busy. * Support saving files to FUSE file systems. * Update known USB scanner IDs. * Add initial Lexmark printers support. * Add ADF duplex support for Brother DS-720. * Fix setting source for Epson scanner. Overview of changes in simple-scan 3.36.1 * Stop disabling compression to fix slow scanning [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. [ Regression Potential ] Changes could break existing functionality. Issue would be confined to simple-scan app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1883819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885744] Re: HIde im-config in application menus/searches
Hello DarkTrick, or anyone else affected, Accepted im-config into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/im- config/0.44-1ubuntu1.1 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: im-config (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1885744 Title: HIde im-config in application menus/searches Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Focal: Fix Committed Bug description: [Impact] I'm refering to this conversation: https://discourse.ubuntu.com/t/improve-presentation-of-input-method-as-search-result-in-all-applications/17031/2 Current situation: === - Settings of im-config can be accomplished by "Language Support" ( see https://ubuntucommunity.s3.dualstack.us-east-2.amazonaws.com/original/2X/4/43cc792173e336454a8d38e3c35b950fbfb48975.png ) - im-config is difficult to understand for "normal users" Suggestion: === Hide im-config from application menu / searches [Test Case] * Open Activities and find that "Input Method" is found * Install im-config from focal-proposed * Open Activities and find that "Input Method" is no longer found [Regression Potential] Minimal; only a tiny change in the .desktop file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1885744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880564] Re: ubuntu-drivers-common now pulls in build tools on end-user systems
Hello Julian, or anyone else affected, Accepted ubuntu-drivers-common into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-drivers-common/1:0.8.4~0.20.04.1 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-drivers-common (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1880564 Title: ubuntu-drivers-common now pulls in build tools on end-user systems Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Bug description: SRU Request: [Test Case] 1) Uninstall the dpkg-dev package. 2) Enable the -proposed repository, and install the new ubuntu- drivers-common (0.8.4~0.20.04.1). 3) Check that the dpkg-dev package was not installed. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The new get_system_architecture() function is very small, and replaces dpkg-architecture for our use-case. ___ In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of build-essential on upgrades (or just binutils and make and patch if you pass --no-install-recommends). This needs to be reverted and fixed differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1880564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'
I can reproduce this issue with the original pulseaudio on a ThinkPad P14s, and after I opened focal-proposed channel and updated the pulseaudio package, this issue was fixed. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887610 Title: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode' Status in HWE Next: New Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Eoan: Won't Fix Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] On some I+N machines (inlcuding lenovo and dell machines), after setting the graphic mode to perofermance mode, and open the gnome sound seting, run suspend/resume test, the audio devices will disappear from UI, instead a dummy audio shows on the UI, and from then on, the audio can't work anymore. [Fix] The root cause is after resuming, the pulseaudio try to recover the PCM device, but at that moment, the devices nodes at /dev/snd/ are not accessible yet sometimes, it will make snd_pcm_open fail and the pulseaudio will calll unload_module to unload alsa audio card. I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(), this will retry the snd_pcm_open() a couple of times if it fails. [Test Case] Install the pulseaudio wit this fix, set the graphic mode to performance mode, open the sound setting, then run suspend/resume 90 times, after test check the audio devices on the UI, the speaker, digital mic are still on the UI, and they could work well. [Regression Risk] Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open() doesn't fail, this patch will not introduce any change, if snd_pcm_open() fails, it just retry a couple of times, so it will not introduce the regression in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878440] Re: gnome-panel - hplip - icon-menu empty
i guess delay is for checking printer-status first before building menu...atm i can live with the workaround, but it should be fixed :) thank you very much -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878440 Title: gnome-panel - hplip - icon-menu empty Status in gnome-flashback package in Ubuntu: Invalid Status in hplip package in Ubuntu: Confirmed Status in indicator-application package in Ubuntu: Confirmed Bug description: in gnome-panel (gnome-flashback) there is an icon for hp-printer (looks like part of indicator-applet), if i click it, a menu is shown, but no readable menuentries. i tried to make screenshot while menu is open, but menu is not visble on this screenshot (seems like it is some kind of overlay). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 17:33:35 2020 InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for HP-Color-LaserJet-MFP-M277dw: socket://192.168.0.200 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1878440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881586] Re: Add support for the new NVIDIA -server driver series
Hello Alberto, or anyone else affected, Accepted ubuntu-drivers-common into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-drivers-common/1:0.8.4~0.20.04.1 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-drivers-common (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1881586 Title: Add support for the new NVIDIA -server driver series Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: Fix Committed Bug description: SRU Request: [Impact] The ubuntu drivers tool requires support for the new NVIDIA -server series (introduced by LP: #1881137) As already made possible when passing in the "--gpgpu" to the "install" argument, ubuntu drivers should be consistent and allow specifying a driver series regardless of whether the --gpgpu argument is used or not. The new parser code takes care of this. [Test Case] 1) Enable the -proposed repository, and install the new ubuntu- drivers-common (0.8.4~0.20.04.1). 2) Check that specifying an NVIDIA driver flavour works (e.g. "ubuntu- drivers install nvidia:440", if your card is supported by the driver) 3) Restart your computer, and see if everything works correctly when accessing the desktop. 4) Remove all the nvidia drivers: sudo apt-get --purge remove '*nvidia*' 5) Test the auto-detection: ubuntu-drivers install 6) Restart your computer, and see if everything works correctly when accessing the desktop. 7) Check that the correct driver was installed for your card: ubuntu-drivers debug [Regression Potential] Medium-Low. The new code should not affect the current functioning of the ubuntu-drivers tool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1881586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825679] Re: Delay/freeze/cpu spike when using the function/media/brightness keys in Xorg
I also had this problem and the suggested workaround helped solving it. Actually, it additionally solved a delay issue on login screen when recovering from suspension and a delay on xdotool commands. Is it possible to reopen this bug report or should I open a new one? -- 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/1825679 Title: Delay/freeze/cpu spike when using the function/media/brightness keys in Xorg Status in gnome-shell package in Ubuntu: Expired Bug description: There is a long time bug when the user press any function key or media key om Gnome, the CPU spikes to 100%, the system freezes for some seconds and then the key is pressed. This is particularly true when change the screen brightness. This only happens in Xorg, Wayland is not affected. On Brazilian keyboard a workaround is to edit the file `/usr/share/X11/xkb/symbols/br` and comment the line `modifier_map Mod3 { Scroll_Lock };` This has been affecting multiple users and has been discussed on https://www.reddit.com/r/gnome/comments/84453o/delayfreezecpu_spike_when_using_the_functionmedia/ https://askubuntu.com/questions/1025302/media-keys-delayed-and-cause-a -cpu-spike-to-100-on-ubuntu-17-10-with-gnome https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on- ubuntu-gnome-17-04?noredirect=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873298] Re: No way to enroll multiple fingers for identification
Tested in gnome-control-center 1:3.36.4-0ubuntu1, using the synaptics sensor in a recent ThinkPad. Multiple fingerprints can be enrolled, it's still possible to remove the fingerprints properly, identification at unlock/login phase still works properly. --- ❯ apt-cache policy gnome-control-center gnome-control-center: Installato: 1:3.36.4-0ubuntu1 Candidato: 1:3.36.4-0ubuntu1 Tabella versione: *** 1:3.36.4-0ubuntu1 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:3.36.1-1ubuntu5 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873298 Title: No way to enroll multiple fingers for identification Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Bug description: * Impact This is the continuation of bug #1865845. In g-c-c user panel, it is not possible to enroll more than one finger for authentication. * Test Case 1. enroll fingerprint in gnome-control-center 2. close the dialog 3. click it again to enroll another finger 4. it shows a dialog requiring you to delete your fingerprints * Impact As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 There will be few new strings, although most of the action events are already covered by the fprintd translations. UI will change quite a lot, but the current documentation [1] should not be affected by the change, being quite generic, but in case it might be updated to be clearer. The change are important improvements and oem request so believe it's right to carry over as a SRU and considered as hardware enablement The new strings are already translatable on launchpad and the translators mailing list has been notified, hopefully we can get some coverage for the new UI in time for the LTS .1 langpack refresh [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878440] Re: gnome-panel - hplip - icon-menu empty
I think real bug is in indicator-application. Definitely not in indicator-applet as it only loads various indicators. I guess it could be fixed also in hplip... For some reason menu is set after some delay - https://git.launchpad.net/ubuntu/+source/hplip/tree/ui5/systemtray.py#n359 ** Changed in: hplip (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878440 Title: gnome-panel - hplip - icon-menu empty Status in gnome-flashback package in Ubuntu: Invalid Status in hplip package in Ubuntu: Confirmed Status in indicator-application package in Ubuntu: Confirmed Bug description: in gnome-panel (gnome-flashback) there is an icon for hp-printer (looks like part of indicator-applet), if i click it, a menu is shown, but no readable menuentries. i tried to make screenshot while menu is open, but menu is not visble on this screenshot (seems like it is some kind of overlay). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 17:33:35 2020 InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for HP-Color-LaserJet-MFP-M277dw: socket://192.168.0.200 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1878440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: New Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED BEHAVIOUR == The pulseaudio snap policy module should correctly determine and enforce it's policy. ACTUAL BEHAVIOUR The pulseaudio snap policy module seemingly at random denies access when the snap has the permissions to do an operation. ADDITIONAL INFORMATION == $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.3 Candidate: 1:13.99.1-1ubuntu3.3 Version table: *** 1:13.99.1-1ubuntu3.3 500 500 http://ch.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://ch.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to:
[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'
** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: pulseaudio (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: pulseaudio (Ubuntu Bionic) Importance: Undecided => High -- 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/1887610 Title: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode' Status in HWE Next: New Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Eoan: Won't Fix Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] On some I+N machines (inlcuding lenovo and dell machines), after setting the graphic mode to perofermance mode, and open the gnome sound seting, run suspend/resume test, the audio devices will disappear from UI, instead a dummy audio shows on the UI, and from then on, the audio can't work anymore. [Fix] The root cause is after resuming, the pulseaudio try to recover the PCM device, but at that moment, the devices nodes at /dev/snd/ are not accessible yet sometimes, it will make snd_pcm_open fail and the pulseaudio will calll unload_module to unload alsa audio card. I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(), this will retry the snd_pcm_open() a couple of times if it fails. [Test Case] Install the pulseaudio wit this fix, set the graphic mode to performance mode, open the sound setting, then run suspend/resume 90 times, after test check the audio devices on the UI, the speaker, digital mic are still on the UI, and they could work well. [Regression Risk] Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open() doesn't fail, this patch will not introduce any change, if snd_pcm_open() fails, it just retry a couple of times, so it will not introduce the regression in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888065] Re: [nvidia] Screen dies/black after changing display orientation or enabling fractional scaling
> Does comment #2 mean the issue is gone for good? No, I just mean that it didn't reoccur after rebooting. Turning on fractional scaling broke things again. The `full-upgrade` thing does appear to have fixed things for good though. Thank you for your help! -- 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/1888065 Title: [nvidia] Screen dies/black after changing display orientation or enabling fractional scaling Status in mutter package in Ubuntu: Incomplete Bug description: I upgraded to 20.04 over a month ago and it's been working fine. I have one monitor (external). I tried turning on fractional scaling in the display settings and the screen immediately turned black. I waited, expecting the "confirm changes" prompt to timeout and restore the display. It never did. Next I hard rebooted, but as soon as I'd entered my password to login, the screen went black again. Tried this a few more times. I then booted to a root console and `apt update/upgrade` to get all updates. Rebooting, I had the same issue on logging in. I then used Ctrl+Alt+F1 to get a virtual console, then back to F2, and a few other things. At some point I was able to log back in. Foolishly I assumed the issue was just with fractional scaling, and back in Display settings I for some reason decided to experiment further and flipped the display orientation to portrate. Immediately I got a black screen and ended back in the same reboot loop, always getting a black screen as soon as I tried to log back in. Searching online I couldn't seem to find a way to revert the display orientation. From another virtual console I was unable to run xrandr or start a wayland session to get to the settings panel. To do that I was trying to run: dbus-run-session -- gnome-shell --display-server --wayland But that's just something I found on the Web, I have no idea what I'm doing there. It just gave the error: (gnome-shell:) mutter-warning: **: Failed to open gpu 'dev/dri/card0 Failed to activate universal planes: Operation not permitted (gnome-shell:) mutter-warning: **: Failed to create backend: No GPUs found Eventually I found a suggestion on the Web to unplug the cable to the display, and after experimenting with that a bit and switching between virtual consoles, at some point it was logged in with a working display ... well, sort of. The colors and icons are weird like it's lost theming or something. Going into the Display settings it seems that the orientation has also been reset to landscape. I'm filing this bug before restarting the machine so I can report the system scan it has taken. At this point I've no idea whether I'll be able to log back in again after a reboot. I'll try that now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..21.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:21:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sat Jul 18 17:21:56 2020 DistUpgraded: 2020-04-29 16:04:33,258 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-37-generic, x86_64: installed nvidia, 435.21, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107GL [Quadro P400] [1028:11be] InstallationDate: Installed on 2019-11-03 (257 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Z4 G4 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=9586ebe6-be5f-4a32-b960-e129e9d98eb9 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-04-29 (80 days ago) dmi.bios.date: 03/21/2019 dmi.bios.vendor: HP dmi.bios.version: P62 v01.75 dmi.board.name: 81C5 dmi.board.vendor: HP dmi.board.version: MVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias:
[Desktop-packages] [Bug 1791588] Re: The test_luks_mount upstream-system test is failing on bionic
The issue isn't there in the current version and serie ** Changed in: udisks2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1791588 Title: The test_luks_mount upstream-system test is failing on bionic Status in udisks2 package in Ubuntu: Fix Released Bug description: Currently udisk2 is failing on all arches for bionic in release. Log of the failing test: == ERROR: test_luks_mount (__main__.Luks) LUKS mount/unmount -- Traceback (most recent call last): File "src/tests/integration-test", line 1367, in test_luks_mount encrypted = self.setup_crypto_device() File "src/tests/integration-test", line 1277, in setup_crypto_device 'label': GLib.Variant('s', 'treasure')})) File "src/tests/integration-test", line 345, in fs_create block.call_format_sync(fs_type, options, None) GLib.GError: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error creating file system: Command-line `mkfs.ext4 -F -L "treasure" "/dev/dm-0"' exited with non-zero exit status 5: stdout: `Creating filesystem with 60416 1k blocks and 15104 inodes Filesystem UUID: e570a38c-ddb3-4d50-a572-1ff0a9886932 Superblock backups stored on blocks: 8193, 24577, 40961, 57345 Allocating group tables: 0/8 done Writing inode tables: 0/8 done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: 0/8 ' stderr: `mke2fs 1.44.1 (24-Mar-2018) Warning, had trouble writing out superblocks. ' (0) -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1791588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's
** Package changed: ubuntu => network-manager (Ubuntu) -- 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/1888390 Title: apparmor error causing deauthentication for certain SSID's Status in network-manager package in Ubuntu: New Bug description: dmesg output: [ 83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/UDisks2" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name=":1.4" pid=1922 label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [ 165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80 [ 165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3) [ 165.568883] wlan0: authenticated [ 165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3) [ 165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 status=0 aid=3) [ 165.579888] wlan0: associated [ 165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice (Reason: 3=DEAUTH_LEAVING) Release Information: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic Expected outcome: Connecting to the home network Actual outcome: deauthentication by local choice (Reason:3=DEAUTH_LEAVING) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1888390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888390] [NEW] apparmor error causing deauthentication for certain SSID's
You have been subscribed to a public bug: dmesg output: [ 83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/UDisks2" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name=":1.4" pid=1922 label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [ 165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80 [ 165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3) [ 165.568883] wlan0: authenticated [ 165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3) [ 165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 status=0 aid=3) [ 165.579888] wlan0: associated [ 165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice (Reason: 3=DEAUTH_LEAVING) Release Information: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic Expected outcome: Connecting to the home network Actual outcome: deauthentication by local choice (Reason:3=DEAUTH_LEAVING) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- apparmor error causing deauthentication for certain SSID's https://bugs.launchpad.net/bugs/1888390 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager 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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
The attachment "This patch is not the fix. WARNING" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Confirmed Status in pcmanfm package in Ubuntu: Triaged Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878440] Re: gnome-panel - hplip - icon-menu empty
the hp-tray-icon is started via gnome startup-applications on console (after killing the tray-application) this works: hp-systray -x & sleep 15 && systemctl --user restart indicator- application.service but if i modify the existing entry to this command-line it does not (maybe this is not executed via shell). i put this into a bash-script and changed the startup-entry to this..now it works as far as i understand you this is still a problem in hplip or more indicator-applet? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878440 Title: gnome-panel - hplip - icon-menu empty Status in gnome-flashback package in Ubuntu: Invalid Status in hplip package in Ubuntu: Invalid Status in indicator-application package in Ubuntu: Confirmed Bug description: in gnome-panel (gnome-flashback) there is an icon for hp-printer (looks like part of indicator-applet), if i click it, a menu is shown, but no readable menuentries. i tried to make screenshot while menu is open, but menu is not visble on this screenshot (seems like it is some kind of overlay). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 17:33:35 2020 InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for HP-Color-LaserJet-MFP-M277dw: socket://192.168.0.200 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1878440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835224] Re: gnome-terminal drops pam_group config
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1835224 Title: gnome-terminal drops pam_group config Status in gnome-terminal package in Ubuntu: Confirmed Bug description: If you use pam_group to add users to a group and open gnome-terminal the dynamic group is lost. How to reproduce: enable pam_group add "*;*;*;Al-2400;dialout" to /etc/security/group.conf log in with a user which is not in the dialout group open gnome-terminal check with id if you in the dialout group ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Wed Jul 3 14:52:29 2019 SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1835224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888392] [NEW] The libreoffice interface does not appear
Public bug reported: When I try to open a document in libreoffice, the application does not open completely. Only the window bar appears. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-core 1:6.4.4-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.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Jul 21 09:26:19 2020 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2020-04-27 (84 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Error demonstration" https://bugs.launchpad.net/bugs/1888392/+attachment/5394609/+files/Captura%20de%20tela%20em%202020-07-21%2009-33-12.png -- 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/1888392 Title: The libreoffice interface does not appear Status in libreoffice package in Ubuntu: New Bug description: When I try to open a document in libreoffice, the application does not open completely. Only the window bar appears. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-core 1:6.4.4-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.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Jul 21 09:26:19 2020 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2020-04-27 (84 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863468] Re: Libreoffice Snap is not available in Turkish
** Changed in: libreoffice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1863468 Title: Libreoffice Snap is not available in Turkish Status in libreoffice package in Ubuntu: Fix Released Bug description: Libreoffice Snap is not available in Turkish. Although there are many other language packs available, there is no Turkish language support. I am having difficulty using it because I do not speak English. I was able to write this message through Google Translate anyway. I request the addition of Turkish language for the Libreoffice Snap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Changed in: jackd2 (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in alsa-plugins package in Ubuntu: Invalid Status in jackd2 package in Ubuntu: Fix Released Status in jackd2 package in Debian: Fix Released Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866498] Re: [Snap] Libreoffice Snap is not available in Hungarian
Thanks a lot, Heather! ** Changed in: libreoffice (Ubuntu) Status: Triaged => Fix Committed -- 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/1866498 Title: [Snap] Libreoffice Snap is not available in Hungarian Status in libreoffice package in Ubuntu: Fix Committed Bug description: Could you please add Hungarian language to libreoffice snap. I want to change all my deb applications to snaps but this isn'T possible without correct localization. Thanks I know it adds ~ 8mb overhead to the snap but I think it's an acceptable size compared to nowadays HDD sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1866498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888380] Re: Give better experience of migration of deb to snap
** Tags added: desktop-lts-wishlist focal ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/1888380 Title: Give better experience of migration of deb to snap Status in chromium-browser package in Ubuntu: Confirmed Bug description: Summary of current state: Back in 19.10 we migrated the deb of chromium to a snap. Users who installed the deb, got snapd and the snap of chromium. Users who already had the deb of chromium, and upgraded, got snapd and the snap. The goal of making the snap was (largely) to reduce the workload on the desktop team in packaging chromium, and to enable the desktop team to publish updates to users very quickly across all supported releases. For users, the goal is to have an up to date chromium browser. For people upgrading, the migration goal was to ensure they kept the browser they'd installed (chromium has never been a default on Ubuntu, but has been on at least one flavour). Feedback from the field: * Some have complained that the Chromium snap has bugs which didn't manifest in the deb (see this very bug tracker) * Some complained that there was no indication that they'd have a deb replaced by a snap (hard to know how many users actually care about this) * Derivative distributions have complained that snapd is being installed "under the covers" or "via the backdoor" (or other pejorative statements) Suggestion for improvement: I believe a fair amount of critique comes from the ignorance of why chromium was migrated to a snap, as most users don't read our blog posts, news articles or release notes. In addition, there's not a tremendous number of user-facing packages which have gone through the deb-to-snap migration, so not a lot of prior art in the field. So it's my believe we should document this better, inform the users better. * At the point of installation of the deb, make it clear that snapd will be installed, followed by the chromium snap (and whatever other content and base snaps are required). * During an upgrade from the deb to the snap, make it clear the deb is being replaced, with similar information to when the snap is installed. * Link to documentation / blog / specific release notes in visible places which makes it clear why this is happening. I'll refrain from suggesting technical solutions because I think we need to discuss the options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1888380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
I applied the patch attached (libX11) but the crash still occurs with less frequency. Maybe i missed some additional patch required to fix this. For the record: I am running LUbuntu in this PC box (upgraded from 16.04 to 18.04) and i have another one with Ubuntu 18.04 + LXDE installed from scratch that doesn't get the error. Anything else i could try? ** Patch added: "This patch is not the fix. WARNING" https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984/+attachment/5394608/+files/Fix-poll_for_response-race-condition.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Confirmed Status in pcmanfm package in Ubuntu: Triaged Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880710] Re: [snap] Tab goes blank even after reloads (and no refresh is happening)
Thanks! I will monitor this bug for updates, I rather use Chromium than Chrome. -- 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/1880710 Title: [snap] Tab goes blank even after reloads (and no refresh is happening) Status in chromium-browser package in Ubuntu: New Bug description: Using chromium from stable: installed: 83.0.4103.61(1165) 163MB after a few hours of having it opened, some tabs started showing a blank page (google spreadsheets, google calendar). Even after hitting F5 or hard reloads, the browser will show the content is being re- fetched, but nothing is rendered. This is happening while chromium is NOT being refreshed: nessita@dali:~$ snap changes ID Status Spawn Ready Summary 125 Doneyesterday at 12:09 -03 yesterday at 12:09 -03 Auto-refresh snap "lxd" nessita@dali:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1880710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871868] Re: Shell dialog text is truncated and ellipsized
** Description changed: + [ Impact ] + + Shell modal dialogs contain text that may be truncated when using + certain locales + + [ Test case ] + + - Start a virtual machine with GNOME Boxes + - The keyboard prompt should be all visible + + [ Regression potential ] + + Text isn't properly rendered or the dialog is not all visible in the + display + + + When trying to start a virtual machine with Gnome Boxes, I get a prompt about keyboard shortcuts. The prompt text is localized, but translated back to English (I think, based on [1]) it says: - Boxes wants to inhibit shortcuts + Boxes wants to inhibit shortcuts - You can restore shortcuts by pressing Super+Escape. + You can restore shortcuts by pressing Super+Escape. In my locale (Finnish), it says - Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa. + Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa. - Voit palauttaa pikanäppäinten toiminnan painamalla Super... + Voit palauttaa pikanäppäinten toiminnan painamalla Super... (sic; see attached photo) So the actual key combination is truncated, defeating the point of that part of the text. This isn't a localization error (AFAICT; see [2]). It's caused by the text being forced to fit on a single line of an arbitrarily fixed width, instead of wrapping to span as many lines as needed. (I'm reporting this against gnome-shell as opposed gnome-boxes based on [3]. Feel free to reassign as necessary.) * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28 * [2] https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036 - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 18:29:14 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-13 (1274 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fi_FI.UTF-8 - SHELL=/bin/bash - RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 - SourcePackage: gnome-shell + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fi_FI.UTF-8 + SHELL=/bin/bash + RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871868 Title: Shell dialog text is truncated and ellipsized Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Bug description: [ Impact ] Shell modal dialogs contain text that may be truncated when using certain locales [ Test case ] - Start a virtual machine with GNOME Boxes - The keyboard prompt should be all visible [ Regression potential ] Text isn't properly rendered or the dialog is not all visible in the display When trying to start a virtual machine with Gnome Boxes, I get a prompt about keyboard shortcuts. The prompt text is localized, but translated back to English (I think, based on [1]) it says: Boxes wants to inhibit shortcuts You can restore shortcuts by pressing Super+Escape. In my locale (Finnish), it says Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa. Voit palauttaa pikanäppäinten toiminnan painamalla Super... (sic; see attached photo) So the actual key combination is truncated, defeating the point of that part of the text. This isn't a localization error (AFAICT; see [2]). It's caused by the text being forced to fit on a single line of an arbitrarily fixed width, instead of wrapping to span as many lines as needed. (I'm reporting this against gnome-shell as opposed gnome-boxes based on [3]. Feel free to reassign as necessary.) * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28 * [2] https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036 ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64
[Desktop-packages] [Bug 1888380] Re: Give better experience of migration of deb to snap
** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1888380 Title: Give better experience of migration of deb to snap Status in chromium-browser package in Ubuntu: New Bug description: Summary of current state: Back in 19.10 we migrated the deb of chromium to a snap. Users who installed the deb, got snapd and the snap of chromium. Users who already had the deb of chromium, and upgraded, got snapd and the snap. The goal of making the snap was (largely) to reduce the workload on the desktop team in packaging chromium, and to enable the desktop team to publish updates to users very quickly across all supported releases. For users, the goal is to have an up to date chromium browser. For people upgrading, the migration goal was to ensure they kept the browser they'd installed (chromium has never been a default on Ubuntu, but has been on at least one flavour). Feedback from the field: * Some have complained that the Chromium snap has bugs which didn't manifest in the deb (see this very bug tracker) * Some complained that there was no indication that they'd have a deb replaced by a snap (hard to know how many users actually care about this) * Derivative distributions have complained that snapd is being installed "under the covers" or "via the backdoor" (or other pejorative statements) Suggestion for improvement: I believe a fair amount of critique comes from the ignorance of why chromium was migrated to a snap, as most users don't read our blog posts, news articles or release notes. In addition, there's not a tremendous number of user-facing packages which have gone through the deb-to-snap migration, so not a lot of prior art in the field. So it's my believe we should document this better, inform the users better. * At the point of installation of the deb, make it clear that snapd will be installed, followed by the chromium snap (and whatever other content and base snaps are required). * During an upgrade from the deb to the snap, make it clear the deb is being replaced, with similar information to when the snap is installed. * Link to documentation / blog / specific release notes in visible places which makes it clear why this is happening. I'll refrain from suggesting technical solutions because I think we need to discuss the options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1888380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist across reboots in resizable VM windows
** Description changed: + [ Impact ] + Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. + + [ Test case ] Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - - After next reboot the setting is reverted to 100% + - After next reboot the setting is reverted to 100%, but should use previous value - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + [ Regression potential ] + + Resolution doesn't adapt properly to the vmware player window size. + + + --- + + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: mutter + SHELL=/bin/bashSourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1884754 Title: Fractional scaling does not persist across reboots in resizable VM windows Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: In Progress Bug description: [ Impact ] Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. [ Test case ] Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - After next reboot the setting is reverted to 100%, but should use previous value [ Regression potential ] Resolution doesn't adapt properly to the vmware player window size. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: 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/1884754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
** Description changed: + [ Impact ] + When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + [ Test case ] + + In a Nvidia system: + - From g-c-c enable fractional scaling + - Set all the available fractional scaling values and ensure they work + + In any case the screen should be turned off + + [ Regression potential ] + + Wrong screen size is set and panning might be enabled. + + --- + + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) - InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) - SourcePackage: mutter + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in mutter source package in Focal: New Status in nvidia-graphics-drivers source package in Focal: Confirmed Bug description: [ Impact ] When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 [ Test case ] In a Nvidia system: - From g-c-c enable fractional scaling - Set all the available fractional scaling values and ensure they work + In any case the screen should be turned off [ Regression potential ] Wrong screen size is set and panning might be enabled. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp