[Desktop-packages] [Bug 1972766] [NEW] Changing default mounting options causes root owner
Public bug reported:
Ubuntu 22.04
If I change the default mounting options in Gnome Disk Utility the owner is
root. This threw me for a loop when all of my git repos were not working. I
thought it was an ubuntu 22.04 problem or a ppa.
It is directly from Gnome Disk Utility by changing the auto mount
options. I don't remember this happening before.
Reproduce
**Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.
**Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share
data.
Change the switch from default mounting options (top switch) to manual
settings. Change label to human readable. ("Data"). Reboot.
Go to your data partition, right click and look at
properties/permissions.
It will say the owner is root and you are not the owner.
**Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings. This
hard to research "mystery setting" is not acceptable for a GUI mounting tool.
Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.
** Affects: gnome-disk-utility (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "fixed data partition settings"
https://bugs.launchpad.net/bugs/1972766/+attachment/5588085/+files/Screenshot%20from%202022-05-10%2012-01-54.png
** Description changed:
- If I change the default mounting options in Gnome Disk Utility the owner
- is root. This threw me for a loop when all of my git repos were not
- working. I thought it was an ubuntu 22.04 problem or a ppa.
+ Ubuntu 22.04
+ If I change the default mounting options in Gnome Disk Utility the owner is
root. This threw me for a loop when all of my git repos were not working. I
thought it was an ubuntu 22.04 problem or a ppa.
It is directly from Gnome Disk Utility by changing the auto mount
options. I don't remember this happening before.
Reproduce
- Control:
+ **Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.
-
- Cause the bug.
+ **Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share
data.
Change the switch from default mounting options (top switch) to manual
settings. Change label to human readable. ("Data"). Reboot.
Go to your data partition, right click and look at
properties/permissions.
It will say the owner is root and you are not the owner.
-
- Fix For The Problem:
+ **Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings.
This hard to research "mystery setting" is not acceptable for a GUI mounting
tool.
Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1972766
Title:
Changing default mounting options causes root owner
Status in gnome-disk-utility package in Ubuntu:
New
Bug description:
Ubuntu 22.04
If I change the default mounting options in Gnome Disk Utility the owner is
root. This threw me for a loop when all of my git repos were not working. I
thought it was an ubuntu 22.04 problem or a ppa.
It is directly from Gnome Disk Utility by changing the auto mount
options. I don't remember this happening before.
Reproduce
**Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.
**Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share
data.
Change the switch from default mounting options (top switch) to manual
settings. Change label to human readable. ("Data"). Reboot.
Go to your data partition, right click and look at
properties/permissions.
It will say the owner is root and you are not the owner.
**Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings.
This hard to research "mystery setting" is not acceptable for a GUI mounting
tool.
Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1972766/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
@Gunnar, I can confirm that the issue is not reproduced under Xorg session, everything works fine this way, thanks! -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972720] Re: Night light does not work on laptop screen when disconnecting from external screen
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972720/+attachment/5588081/+files/prevjournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972720 Title: Night light does not work on laptop screen when disconnecting from external screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I turn on my laptop while it is connected to an external screen (my display settings are such that only the external screen is used while it is connected) and later disconnect it, Night Light does not work on the laptop screen (it did on the external screen). I have Night Light on "Manual Schedule" from 00:00 to 23:59 so it would always be on. Turning the Night Light setting off and on again does not help. After restarting the laptop while it is not connected to the external screen, Night Light will work as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 21:27:17 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-01-09 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972720] Re: Night light does not work on laptop screen when disconnecting from external screen
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972720/+attachment/5588079/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972720 Title: Night light does not work on laptop screen when disconnecting from external screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I turn on my laptop while it is connected to an external screen (my display settings are such that only the external screen is used while it is connected) and later disconnect it, Night Light does not work on the laptop screen (it did on the external screen). I have Night Light on "Manual Schedule" from 00:00 to 23:59 so it would always be on. Turning the Night Light setting off and on again does not help. After restarting the laptop while it is not connected to the external screen, Night Light will work as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 21:27:17 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-01-09 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972720] Re: Night light does not work on laptop screen when disconnecting from external screen
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972720/+attachment/5588080/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972720 Title: Night light does not work on laptop screen when disconnecting from external screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I turn on my laptop while it is connected to an external screen (my display settings are such that only the external screen is used while it is connected) and later disconnect it, Night Light does not work on the laptop screen (it did on the external screen). I have Night Light on "Manual Schedule" from 00:00 to 23:59 so it would always be on. Turning the Night Light setting off and on again does not help. After restarting the laptop while it is not connected to the external screen, Night Light will work as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 21:27:17 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-01-09 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972763] [NEW] Control sound missing for volume keys
Public bug reported: Cf. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/508 Seems to be another regression issue with Jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue May 10 07:08:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-31 (1712 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-25 (14 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1972763 Title: Control sound missing for volume keys Status in gnome-shell package in Ubuntu: New Bug description: Cf. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/508 Seems to be another regression issue with Jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue May 10 07:08:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-31 (1712 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-25 (14 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972749] Re: Multiple Xsessions doesn't work
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1972749 Title: Multiple Xsessions doesn't work Status in xorg package in Ubuntu: New Bug description: On my system with Nvidia 510 drivers I found that if I'm logged in and lock the session another user can't login. I reset the 2nd user's account to verify that if I login and lock my session they can't login. I found this in permission error in the logs. May 09 21:58:20 x1 gnome-shell[17718]: Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix" I've confirmed that /tmp/.X11-unix is owned by the 1st user, so something seems to be causing the system to use the same tmp directory for both users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:14:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.17.6, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] [1458:401a] MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vg-root ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: PRIME H270-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/11/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH270-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 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:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1972749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972749] [NEW] Multiple Xsessions doesn't work
You have been subscribed to a public bug: On my system with Nvidia 510 drivers I found that if I'm logged in and lock the session another user can't login. I reset the 2nd user's account to verify that if I login and lock my session they can't login. I found this in permission error in the logs. May 09 21:58:20 x1 gnome-shell[17718]: Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix" I've confirmed that /tmp/.X11-unix is owned by the 1st user, so something seems to be causing the system to use the same tmp directory for both users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:14:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.17.6, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] [1458:401a] MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vg-root ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: PRIME H270-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/11/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH270-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 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:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash jammy ubuntu -- Multiple Xsessions doesn't work https://bugs.launchpad.net/bugs/1972749 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972720] Re: Night light does not work on laptop screen when disconnecting from external screen
Thanks for the bug report. Please run: lspci -k > lspci.txt journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. ** Tags added: gamma ** 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/1972720 Title: Night light does not work on laptop screen when disconnecting from external screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I turn on my laptop while it is connected to an external screen (my display settings are such that only the external screen is used while it is connected) and later disconnect it, Night Light does not work on the laptop screen (it did on the external screen). I have Night Light on "Manual Schedule" from 00:00 to 23:59 so it would always be on. Turning the Night Light setting off and on again does not help. After restarting the laptop while it is not connected to the external screen, Night Light will work as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 21:27:17 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-01-09 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
I should note that regular Ubuntu 22.04 only has 'adwaita-icon-theme' installed, not 'adwaita-icon-theme-full'. To figure out which login screen it is that needs the latter, please: 1. Attach a photo of the login screen. 2. Run: dpkg -l > packages.txt and attach the resulting text file here. ** Summary changed: - [mgag200] Mouse cursor is a semi-opaque white square + [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full) ** No longer affects: linux (Ubuntu) ** Package changed: mutter (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita- icon-theme-full) Status in Ubuntu: Incomplete Bug description: Do not think this is hardware dependent, but I'm using an HPE MicroServer Gen10 Plus. I installed the server edition of 22.04. Post-Installation, I added some desktop environments. After logging in, these are working fine. However on the gdm login entry and password entry screens I had no mouse pointer icon. A semi-opaque white square tracked the mouse movements. My reading suggested that gdm defaults to using the cursor icon theme provided by the adwaita-icon-theme package. I discovered this theme comes in two sizes, a basic, smaller package installed automatically and a larger "full" package. $ apt list 'adwaita-icon-theme*' Listing... Done adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic] adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed] $ The gdm mouse pointer appears and disappears with installation and removal of the package "adwaita-icon-theme-full". Either gdm's dependencies should include the "full" package OR the appropriate mouse pointer icons should be moved from the full to the basic "adwaita-icon-theme" package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: File dialog not displayed within screen range
Is it after suspend/resume/unlocking the screen? (bug 1961508) -- 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/1972151 Title: File dialog not displayed within screen range Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972059] Re: One screen does not come back from lock
I can't see anything immediately wrong in that log. Next time the problem happens please note the exact time it happened at, and then collect a new log covering that time period: journalctl -b0 > journal.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/1972059 Title: One screen does not come back from lock Status in mutter package in Ubuntu: Incomplete Bug description: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969815] Re: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state
If you can only afford to try one kernel then please make it drm-tip: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm- tip/2022-05-08/amd64/ That will tell us if the bug already has a fix upstream. Although you won't get automatic updates for that kernel so may want to uninstall the packages after you've finished testing them. -- 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/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
> Using Wayland seems to solve the issue, but there are still programs > like OBS that I need to use that can't capture the desktop That was meant to be fixed in OBS Studio 27 (bug 1838967). If it's not working in Ubuntu 22.04 then please open a new bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Unknown Status in metacity package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click
You don't need to disable Wayland completely, just select 'Ubuntu on Xorg' on the login screen and your choice will be remembered for future logins. -- 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/1725814 Title: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Focal: Invalid Bug description: Honestly I have no idea which package this is in and I could not identify it by following the wiki page for identifying packages. I had no luck with the ubuntu-bug command either. Feel free to migrate at your discretion. The Activities menu/button at the top left in the desktop menu(?) bar seems to listen to left-mouse-up instead of a full click with the mouse. If I want to e.g. select all my files on the desktop by click-and- dragging a selection box and then end the selection at the top left of the screen I will then also activate the Activities button if I release the mouse button over it. I expect most button-like UI controls to only trigger on complete mouse clicks: mouse down, mouse up. Pretty much the *only* exception to this expectation -- that I can think of -- is when a click is initiated on one menu item and finishes on a menu item that is its peer. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1725814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972726] Re: Update mutter to 42.1
https://bugs.launchpad.net/ubuntu/+source/mutter/+bugs?field.tag=fixed- in-42.1 -- 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/1972726 Title: Update mutter to 42.1 Status in mutter package in Ubuntu: Triaged Status in mutter source package in Jammy: Incomplete Bug description: Impact -- Test Case - What Could Go Wrong --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972728] Re: Night light not working on Nvidia Wayland
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #290 https://gitlab.gnome.org/GNOME/mutter/-/issues/290 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/290 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => nvidia-graphics-drivers-510 (Ubuntu) ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided => Medium ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Triaged ** Tags added: nvidia nvidia-wayland -- 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/1972728 Title: Night light not working on Nvidia Wayland Status in Mutter: Unknown Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: On the Wayland session using an Nvidia GPU, enabling the Night Light setting in the Settings app doesn't change the screen colour temperature to a warmer hue regardless of "Sunset to Sunrise" or "Manual Schedule" being selected. Switching to the X11 session results in Night Light working as expecting. I'm currently using the Nvidia 510.60.02 driver (RTX 2080Ti). $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:01:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-29 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 387957] Re: Improve Save As Dialog Box (focus issues)
Just adding my support to those rallying for change on this issue. I tried colas' script in the background, but whilst it does report that it's resetting location-mode, it doesn't seem to be solving the problem for me (on Jammy Jellyfish). I also noticed there's another schema/key, org.gtk.gtk4.Settings.FileChooser location-mode so I tried running two copies of the script to cover both keys, but that's still not giving me any joy. Perhaps the issue is that I'm using awesomewm, but it's the same Save As dialog I'd have thought. Either way - this is far and away the worst feature of Ubuntu for me - it bothers me every time I use it. My personal feeling is that all other cosmetic development on Ubuntu should be stopped until this issue - that must be used thousands - maybe millions? of times a day - is fixed. Thanks to all those above who've pushed for this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/387957 Title: Improve Save As Dialog Box (focus issues) Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: The save dialog box has the irritating habit of not focusing on the file name area once I have browsed to the location where I would like to save my document. This is done better in Windows. There are two main scenarios when saving a document where this behaviour annoys: Scanario 1 - Browsing to save location by double-clicking: 1. File -> Save As (to bring up the "Save" dialog box). 2. Double click on the folder in which you would like to save the document. 3. Notice that the focus is now in the folder list area, not on the file name area. 4. I now have to click in the file name area to be able to name my document. In Windows, the focus is returned immediately to the file name box once a folder is double clicked, so the name can be typed and the document saved in one step. Scenario 2 - Browsing save location using the keyboard (find as you type): 1. File -> Save As (to bring up the "Save" dialog box). 2. Click on the folder area so that folder names can be typed to find them. Hit enter to enter desired folder. 3. Within the folder, step 2 can be repeated for subfolders indefinitely. 4. Once the desired location has been reached, the user must use the mouse click in the file name area to name the file before saving. In Windows, when using find as you type, although focus is retained by the folder area when entering a lower folder level (so that you can browse to another level using the keyboard if desired), jumping to the file name box is simply a matter of pressing tab ONCE. In Ubuntu, I have to reverse tab (shift-tab) around 10 times to get back to the file name box at the top of the screen, or use the mouse - most annoying. Solutions (copy the Windows behaviour): 1. If a folder is double clicked with the mouse, the focus should jump back to the file name box. 2. If a folder is entered into by pressing enter (on the keyboard), focus should remain in the folder area, but the file name box should only be a single tab away. I understand that solution 2 is problematic in that tabbing would ordinarily jump to the next element (usually the "file type" dropdown), not back to the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
@Sergii: Can you please log in to an Ubuntu on Xorg session and let us know if you see the issue there as well. -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972114]
Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures ** Tags added: community-security ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1972114 Title: Pressing Ctl Alt F7 allows me to bypass lock screen Status in lightdm package in Ubuntu: New Bug description: When I hid Ctl Alt f7 after locking the screen or starting the pc up from a suspended state it just takes me to my desktop without requiring a password. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun May 8 20:35:50 2022 InstallationDate: Installed on 2022-03-12 (57 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: lightdm UpgradeStatus: Upgraded to jammy on 2022-04-29 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1972114/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972726] Re: Update mutter to 42.1
** Changed in: mutter (Ubuntu) Status: Fix Committed => Triaged -- 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/1972726 Title: Update mutter to 42.1 Status in mutter package in Ubuntu: Triaged Status in mutter source package in Jammy: Incomplete Bug description: Impact -- Test Case - What Could Go Wrong --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
Solution https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/22 didn't worked for me. Installing this https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 didn't worked for me as well. Downgraded following instructions from https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/51 and then reboot worked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: Fix Released Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
> Should be part of the 'beacon' info. https://howiwifi.com/2020/07/13/802-11-frame-types-and-formats/ has a good overview. I discovered this exchange while observing 'on the wire' with wireshark. Thanks for the link; lots of useful stuff there! > > I wondered if perhaps it this only works on some APs? > That is the impression that I get, the country code info is part of the management frames transmitted by the AP, could be unsupported, not configured, or mis-configured. Okay, to my mind that brings us back to "need option to specify wifi regulatory domain". It seems the situation with netplan/networkd is "there's no option", and in NetworkManager is "there's no option, but *sometimes* it'll magically work anyway" (although you'll need to go digging in the logs to confirm that :) -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: New Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: New Status in netplan.io source package in Kinetic: Triaged Status in network-manager source package in Kinetic: New Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972728] [NEW] Night light not working on Nvidia Wayland
Public bug reported: On the Wayland session using an Nvidia GPU, enabling the Night Light setting in the Settings app doesn't change the screen colour temperature to a warmer hue regardless of "Sunset to Sunrise" or "Manual Schedule" being selected. Switching to the X11 session results in Night Light working as expecting. I'm currently using the Nvidia 510.60.02 driver (RTX 2080Ti). $ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:01:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-29 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1972728 Title: Night light not working on Nvidia Wayland Status in gnome-shell package in Ubuntu: New Bug description: On the Wayland session using an Nvidia GPU, enabling the Night Light setting in the Settings app doesn't change the screen colour temperature to a warmer hue regardless of "Sunset to Sunrise" or "Manual Schedule" being selected. Switching to the X11 session results in Night Light working as expecting. I'm currently using the Nvidia 510.60.02 driver (RTX 2080Ti). $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:01:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-29 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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/1972728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972726] [NEW] Update mutter to 42.1
Public bug reported: Impact -- Test Case - What Could Go Wrong --- ** Affects: mutter (Ubuntu) Importance: High Status: Fix Committed ** Affects: mutter (Ubuntu Jammy) Importance: High Assignee: Jeremy Bicha (jbicha) Status: Incomplete ** Tags: jammy upgrade-software-version ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => High ** Changed in: mutter (Ubuntu Jammy) Status: New => Incomplete ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- 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/1972726 Title: Update mutter to 42.1 Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Incomplete Bug description: Impact -- Test Case - What Could Go Wrong --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+attachment/5587972/+files/Xorg.0.log -- 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/1972037 Title: Stack Overflow - gnome-control-center Status in gnome-control-center package in Ubuntu: New Bug description: Program: gnome-control-center Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) OS: ubuntu 20.04.4 LTS GNOME Version: 3.36.8 (ubuntu default download) Windowing System: X11 Graphics: GeForce 8400GS/PCIe/SSE2 Driver: Using NVIDIA binary driver version 340.108 Source: download version from ubuntu Steps to reproduce: Reset GNOME settings with: dconf reset -f /org/gnome/control-center/ Open GNOME Settings with: /usr/bin/gnome-control-center Click on "Displays" and receive: Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Segmentation fault (core dumped) Repeated using gdb with package symbols. Output of "bt -full" in attachment (with a few comments). (Submitted to gnome.org, but they said it is out of date and not supported by them.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 6 20:38:55 2022 InstallationDate: Installed on 2011-07-11 (3952 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
@Gunnar, thanks for the information. The output looks correct:
sergii@shdlthnk:~$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'us'), ('xkb', 'ua'), ('xkb', 'ru')]
But actually the switching process looks like this:
sergii@shdlthnk:~$ asdf asdf фіва фыва
I pressed ctrl+shift after each four letters, i.e. after first press I'm
still on English layout, then Ukrainian after the second and on Russian
after the last.
And if I try to remove all layouts except English via standard Settings
dialog, I'm still able to switch between these three.
I don't if this behavior is related to the issue being discussed,
though, just my observation.
--
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/1956916
Title:
Using certain xkb-options, e.g. Alt+Shift, for switching input sources
not reflected by the input source indicator in a wayland session
Status in gnome-control-center package in Ubuntu:
Confirmed
Bug description:
Currently, there is no way to define Left Alt + Left Shift key combination to
change keyboard layouts in Ubuntu 22.04. In previous versions there was a
convenient "Keyboard Layout Options" window in which there was able to set
required key combination. Since 22.04 release I can't find a way to do that
because useless "Keyboard Shortcuts" window opens instead in which unable to
set Left Alt + Left Shift as "Switch to the next source" shortcut.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2022-01-07 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230)
NonfreeKernelModules: nvidia_modeset nvidia
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Tags: jammy wayland-session ubiquity-22.04.3
Uname: Linux 5.13.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972721] [NEW] Include gtk3 changes needed for mutter 42.1
Public bug reported: Impact -- We need to update gtk3 before updating mutter to 42.1. Otherwise, in gtk3 apps like gedit, it's not possible to scroll past the cursor position. The mutter issue with more details is https://gitlab.gnome.org/GNOME/mutter/-/issues/2261 We need to update mutter 42.1 since it includes a lot of bug fixes. GNOME Shell 42.1 (with the corresponding changes to mutter, gtk3 and gtk4) will better comply with the Wayland specifications. The gtk4 bug is LP: #1972722 Test Case - Install the updated gtk3 packages. Use gedit to open a long text file. Scroll down past the page break. The document should scroll normally. What Could Go Wrong --- Ideally, GNOME would have done a new GTK3 release for this issue. They will eventually, but it seems better for Ubuntu to be proactive and not further delay the mutter/gnome-shell 42.1 releases. These commits are cherry-picks from the stable branch https://gitlab.gnome.org/GNOME/gtk/-/commits/gtk-3-24/ NOTE To avoid a temporary mismatch related to phased updates, we want this update to be 100% phased before releasing mutter 42.1 to jammy-updates. ** Affects: gtk+3.0 (Ubuntu) Importance: High Status: Fix Committed ** Affects: gtk+3.0 (Ubuntu Jammy) Importance: High Assignee: Jeremy Bicha (jbicha) Status: In Progress ** Tags: jammy ** Also affects: gtk+3.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: gtk+3.0 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gtk+3.0 (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bicha (jbicha) ** Description changed: Impact -- We need to update gtk3 before updating mutter to 42.1. Otherwise, in gtk3 apps like gedit, it's not possible to scroll past the cursor position. The mutter issue with more details is https://gitlab.gnome.org/GNOME/mutter/-/issues/2261 We need to update mutter 42.1 since it includes a lot of bug fixes. GNOME Shell 42.1 (with the corresponding changes to mutter, gtk3 and gtk4) will better comply with the Wayland specifications. - The gtk4 bug is LP: # - + The gtk4 bug is LP: #1972722 Test Case - Install the updated gtk3 packages. Use gedit to open a long text file. Scroll down past the page break. The document should scroll normally. What Could Go Wrong --- Ideally, GNOME would have done a new GTK3 release for this issue. They will eventually, but it seems better for Ubuntu to be proactive and not further delay the mutter/gnome-shell 42.1 releases. These commits are cherry-picks from the stable branch https://gitlab.gnome.org/GNOME/gtk/-/commits/gtk-3-24/ NOTE To avoid a temporary mismatch related to phased updates, we want this update to be 100% phased before releasing mutter 42.1 to jammy-updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972721 Title: Include gtk3 changes needed for mutter 42.1 Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Jammy: In Progress Bug description: Impact -- We need to update gtk3 before updating mutter to 42.1. Otherwise, in gtk3 apps like gedit, it's not possible to scroll past the cursor position. The mutter issue with more details is https://gitlab.gnome.org/GNOME/mutter/-/issues/2261 We need to update mutter 42.1 since it includes a lot of bug fixes. GNOME Shell 42.1 (with the corresponding changes to mutter, gtk3 and gtk4) will better comply with the Wayland specifications. The gtk4 bug is LP: #1972722 Test Case - Install the updated gtk3 packages. Use gedit to open a long text file. Scroll down past the page break. The document should scroll normally. What Could Go Wrong --- Ideally, GNOME would have done a new GTK3 release for this issue. They will eventually, but it seems better for Ubuntu to be proactive and not further delay the mutter/gnome-shell 42.1 releases. These commits are cherry-picks from the stable branch https://gitlab.gnome.org/GNOME/gtk/-/commits/gtk-3-24/ NOTE To avoid a temporary mismatch related to phased updates, we want this update to be 100% phased before releasing mutter 42.1 to jammy-updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1972721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972722] [NEW] Include gtk4 changes needed for mutter 42.1
Public bug reported: Impact -- We need to update gtk4 before updating mutter to 42.1. Otherwise, in gtk3 apps like gnome-text-editor, it's not possible to scroll past the cursor position. The mutter issue with more details is https://gitlab.gnome.org/GNOME/mutter/-/issues/2261 We need to update mutter 42.1 since it includes a lot of bug fixes. GNOME Shell 42.1 (with the corresponding changes to mutter, gtk3 and gtk4) will better comply with the Wayland specifications. The gtk3 bug is LP: #1972721 Test Case - Install the updated gtk4 packages. Use gnome-text-editor to open a long text file. Scroll down past the page break. The document should scroll normally. What Could Go Wrong --- Ideally, GNOME would have done a new GTK4 release for this issue. They will eventually, but it seems better for Ubuntu to be proactive and not further delay the mutter/gnome-shell 42.1 releases. These commits are cherry-picks from the stable branch https://gitlab.gnome.org/GNOME/gtk/-/commits/gtk-4-6 NOTE To avoid a temporary mismatch related to phased updates, we want this update to be 100% phased before releasing mutter 42.1 to jammy-updates. ** Affects: gtk4 (Ubuntu) Importance: High Status: Fix Committed ** Affects: gtk4 (Ubuntu Jammy) Importance: High Assignee: Jeremy Bicha (jbicha) Status: In Progress ** Tags: jammy ** Also affects: gtk4 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gtk4 (Ubuntu Jammy) Status: New => In Progress ** Changed in: gtk4 (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1972722 Title: Include gtk4 changes needed for mutter 42.1 Status in gtk4 package in Ubuntu: Fix Committed Status in gtk4 source package in Jammy: In Progress Bug description: Impact -- We need to update gtk4 before updating mutter to 42.1. Otherwise, in gtk3 apps like gnome-text-editor, it's not possible to scroll past the cursor position. The mutter issue with more details is https://gitlab.gnome.org/GNOME/mutter/-/issues/2261 We need to update mutter 42.1 since it includes a lot of bug fixes. GNOME Shell 42.1 (with the corresponding changes to mutter, gtk3 and gtk4) will better comply with the Wayland specifications. The gtk3 bug is LP: #1972721 Test Case - Install the updated gtk4 packages. Use gnome-text-editor to open a long text file. Scroll down past the page break. The document should scroll normally. What Could Go Wrong --- Ideally, GNOME would have done a new GTK4 release for this issue. They will eventually, but it seems better for Ubuntu to be proactive and not further delay the mutter/gnome-shell 42.1 releases. These commits are cherry-picks from the stable branch https://gitlab.gnome.org/GNOME/gtk/-/commits/gtk-4-6 NOTE To avoid a temporary mismatch related to phased updates, we want this update to be 100% phased before releasing mutter 42.1 to jammy-updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1972722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972720] Re: Night light does not work on laptop screen when disconnecting from external screen
** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1972720 Title: Night light does not work on laptop screen when disconnecting from external screen Status in gnome-shell package in Ubuntu: New Bug description: When I turn on my laptop while it is connected to an external screen (my display settings are such that only the external screen is used while it is connected) and later disconnect it, Night Light does not work on the laptop screen (it did on the external screen). I have Night Light on "Manual Schedule" from 00:00 to 23:59 so it would always be on. Turning the Night Light setting off and on again does not help. After restarting the laptop while it is not connected to the external screen, Night Light will work as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 21:27:17 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-01-09 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
@Sergii: To find out which layouts you actually have, you can run this command: gsettings get org.gnome.desktop.input-sources sources -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972720] [NEW] Night light does not work on laptop screen when disconnecting from external screen
You have been subscribed to a public bug: When I turn on my laptop while it is connected to an external screen (my display settings are such that only the external screen is used while it is connected) and later disconnect it, Night Light does not work on the laptop screen (it did on the external screen). I have Night Light on "Manual Schedule" from 00:00 to 23:59 so it would always be on. Turning the Night Light setting off and on again does not help. After restarting the laptop while it is not connected to the external screen, Night Light will work as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 21:27:17 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-01-09 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- Night light does not work on laptop screen when disconnecting from external screen https://bugs.launchpad.net/bugs/1972720 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
My system is also affected by this bug, it seems, after I upgraded from 21.10 to 22.04 LTS (and yes, it looks I'm using Wayland too). Also there's one strange feature that I did notice beside keyboard indicator itself. I have three layout (english, ukrainian and russian). On the 21.10 system, single ctrl+shift combination switched from one layout to the next, but now I need to type ctrl+switch twice to switch from english to ukrainian. It looks like I have two english layouts now, then ukrainian and then russian. However, I didn't add any languages during or after the upgrade. -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1677050] GOOD DAY!
Hope this email finds you well! Been thinking of you lately. Please let me know when you get this, I'd like to ask you something. Stay safe and healthy, Jim -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1677050 Title: Youtube video will not run Status in xorg package in Ubuntu: Invalid Bug description: When I first set up ubuntu I was able to look at youtube videos, but then they just stopped running. I have no real idea why. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-82.90-generic 3.19.8-ckt22 Uname: Linux 3.19.0-82-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 28 16:44:30 2017 DistUpgraded: 2017-02-13 13:49:16,446 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a5e] InstallationDate: Installed on 2015-12-03 (481 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion GC670AA-ABA a6120n ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-82-generic root=UUID=38cc240f-f1a8-40ed-98a0-6c59680dea14 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2017-02-13 (43 days ago) dmi.bios.date: 06/07/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.20 dmi.board.name: Leonite2 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 6.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.20:bd06/07/2007:svnHP-Pavilion:pnGC670AA-ABAa6120n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: GC670AA-ABA a6120n dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Mar 28 15:50:33 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputGenPS/2 Genius Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 27137 vendor VSC xserver.version: 2:1.17.1-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1677050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square
Adding MUTTER_DEBUG_DISABLE_HW_CURSORS=1 to /etc/environment and rebooting had no effect on the issue. White square "mouse pointer" is present on gdm login screen if /usr/share/icons/adwaita/cursors is missing (renamed). If instead I install a symbolic link .../Adwaita/cursors -> .../Yaru/cursors and restart gdm I get valid mouse pointers. gdm is clearly looking for its cursor files in the Adwaita theme directory rather than Yaru. -- 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/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: Do not think this is hardware dependent, but I'm using an HPE MicroServer Gen10 Plus. I installed the server edition of 22.04. Post-Installation, I added some desktop environments. After logging in, these are working fine. However on the gdm login entry and password entry screens I had no mouse pointer icon. A semi-opaque white square tracked the mouse movements. My reading suggested that gdm defaults to using the cursor icon theme provided by the adwaita-icon-theme package. I discovered this theme comes in two sizes, a basic, smaller package installed automatically and a larger "full" package. $ apt list 'adwaita-icon-theme*' Listing... Done adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic] adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed] $ The gdm mouse pointer appears and disappears with installation and removal of the package "adwaita-icon-theme-full". Either gdm's dependencies should include the "full" package OR the appropriate mouse pointer icons should be moved from the full to the basic "adwaita-icon-theme" package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
@Anton: If I understand it correctly, in that Ask Ubuntu answer you basically confirm the presence of this bug as worded in the bug summary. (I assume you are using wayland.) And yes, Win/Super + Space is another thing. It's the default shortcut on GNOME to switch input source, and uses another mechanism compared to the shortcuts you can set in Tweaks. -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972123] Re: Online accounts crashes on sign in
Thanks for the catch. I wasn't aware of the risks involved with crash files and the fact that ubuntu-bug will make the report private. Maybe a warning should be emitted by launchpad on upload of this file type? ubuntu-bug is quite annoying and always opens a new tab which is in the wrong Firefox container. I filed bug 1972718 for that. Step 1 didn't work, couldn't find the crash report by step 2, and step 3 worked without a reboot or reproducing. The new bug is bug 1972717. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1972123 Title: Online accounts crashes on sign in Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: I noticed that my to-dos weren't syncing, so I checked online accounts and there's this triangle warning icon. I click into it and it says "Credentials have expired", "Sign in to enable this account." Now when I click "Sign in", the pop up changes to a frozen progress bar on top and with empty content, then crashes after a few seconds. Now I can't sync anything and can't fix it. Ubuntu 22.04 LTS, Wayland on Nvidia 510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1972123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972123] Re: Online accounts crashes on sign in
** Attachment removed: "_usr_bin_gnome-control-center.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1972123/+attachment/5587728/+files/_usr_bin_gnome-control-center.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1972123 Title: Online accounts crashes on sign in Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: I noticed that my to-dos weren't syncing, so I checked online accounts and there's this triangle warning icon. I click into it and it says "Credentials have expired", "Sign in to enable this account." Now when I click "Sign in", the pop up changes to a frozen progress bar on top and with empty content, then crashes after a few seconds. Now I can't sync anything and can't fix it. Ubuntu 22.04 LTS, Wayland on Nvidia 510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1972123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
I was able to configure switching languages input by Alt + Shift combination in Ubuntu 22.04 by instruction here - https://askubuntu.com/a/1407561/1548713 -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969815] Re: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state
Thanks for that, will try it. However my box is AMD therefore 1. no onboard video and 2. no Intel. Back to your request of installing an older kernel: I might have found a maintenance window. Given that I did, would you like for me to try any one? I understand you mentioned to install any of them but if we would have *1* shot, would we have any preference in terms of tag? Of course, I would need to stick to v5.something and possibly v5.1x.? -- 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/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to:
[Desktop-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
Having this issue as same as Kes describes. Can be reproduced under Xorg environment running Nvidia 510 drivers and Ubuntu 22.04. Did not have this issue under 20.04. If I have a youtube video running the chrome window lags and the terminal window lags while moving them. If I have this page open it moves without lag. I tried to disable Desktop Icons NG, it helped the issue a bit, but there is still extreme lag. Using Wayland seems to solve the issue, but there are still programs like OBS that I need to use that can't capture the desktop ( not related to this ). Running glxgears also give me lag while moving the window. Let me know if you need me to try something specific that might help you get more data out. INXI dump: System: Host: X Kernel: 5.15.0-27-generic x86_64 bits: 64 Desktop: GNOME 42.0 Distro: Ubuntu 22.04 LTS (Jammy Jellyfish) Machine: Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-F GAMING v: Rev X.0x serial: UEFI: American Megatrends v: 4021 date: 08/09/2021 CPU: Info: 16-core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP cache: L2: 8 MiB Speed (MHz): avg: 3400 min/max: N/A cores: 1: 3394 2: 3394 3: 3394 4: 3394 5: 3394 6: 3394 7: 3394 8: 3394 9: 3394 10: 3394 11: 3394 12: 3394 13: 3394 14: 3394 15: 3394 16: 3394 17: 3394 18: 3394 19: 3394 20: 3394 21: 3394 22: 3394 23: 3394 24: 3593 25: 3394 26: 3394 27: 3394 28: 3394 29: 3394 30: 3394 31: 3394 32: 3394 Graphics: Device-1: NVIDIA GA102 [GeForce RTX 3080] driver: nvidia v: 510.60.02 Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia gpu: nvidia resolution: 1: 5120x1440~120Hz OpenGL: renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2 v: 4.6.0 NVIDIA 510.60.02 Sensors: System Temperatures: cpu: 34.5 C mobo: 34.0 C gpu: nvidia temp: 33 C Fan Speeds (RPM): fan-1: 0 fan-2: 1081 fan-3: 1135 fan-4: 1359 fan-5: 4753 fan-6: 1227 gpu: nvidia fan: 0% Info: Processes: 529 Uptime: 1d 4h 23m Memory: 31.26 GiB used: 4.54 GiB (14.5%) Shell: Bash inxi: 3.3.13 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Unknown Status in metacity package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972059] Re: One screen does not come back from lock
I would like to amend the description of the problem. It happened twice today. I press a kew, and the screen comes back, with the password request, but it is "frozen". If I move the mouse, it only moves on the other screen, and no typing happens. After doing some Ctrl-Alt-F. I land on the "select users" screen and it works again. -- 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/1972059 Title: One screen does not come back from lock Status in mutter package in Ubuntu: Incomplete Bug description: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click
Hello, Daniel. Yep, I didn't want to open a duplicate. By the way, the current workaround for this is to disable Wayland: 1. sudo vi /etc/gdm3/custom.conf 2. WaylandEnable=false 3. Reboot -- 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/1725814 Title: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Focal: Invalid Bug description: Honestly I have no idea which package this is in and I could not identify it by following the wiki page for identifying packages. I had no luck with the ubuntu-bug command either. Feel free to migrate at your discretion. The Activities menu/button at the top left in the desktop menu(?) bar seems to listen to left-mouse-up instead of a full click with the mouse. If I want to e.g. select all my files on the desktop by click-and- dragging a selection box and then end the selection at the top left of the screen I will then also activate the Activities button if I release the mouse button over it. I expect most button-like UI controls to only trigger on complete mouse clicks: mouse down, mouse up. Pretty much the *only* exception to this expectation -- that I can think of -- is when a click is initiated on one menu item and finishes on a menu item that is its peer. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1725814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972711] [NEW] Videos (totem) corrupt video playback mkv/h264
Public bug reported: playback of mkv/h264 is corrupt. Works fine in VLC Description:Ubuntu 22.04 LTS Release:22.04 totem: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Wayland, HD Graphics 4000 Kernel: 5.17.0-1003-oem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 9 08:52:21 2022 InstallationDate: Installed on 2021-02-06 (456 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1972711/+attachment/5587941/+files/Screenshot%20from%202022-05-09%2008-51-58.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972711 Title: Videos (totem) corrupt video playback mkv/h264 Status in gstreamer1.0 package in Ubuntu: New Bug description: playback of mkv/h264 is corrupt. Works fine in VLC Description: Ubuntu 22.04 LTS Release: 22.04 totem: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Wayland, HD Graphics 4000 Kernel: 5.17.0-1003-oem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 9 08:52:21 2022 InstallationDate: Installed on 2021-02-06 (456 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972708] [NEW] Wired connection is off after resuming from sleep
Public bug reported:
When coming out of sleep mode, the wired connection is always off, fresh
installation of 22.04. It goes up easily by toggling it on from the UI
("Turn On")
Relevant /var/log/syslog messages:
May 9 17:11:49 olivier-desktop kernel: [12935.927375] Bluetooth: hci0: Timed
out waiting for suspend events
May 9 17:11:49 olivier-desktop kernel: [12935.927381] Bluetooth: hci0: Suspend
timeout bit: 6
May 9 17:11:49 olivier-desktop kernel: [12935.927395] Bluetooth: hci0: Suspend
notifier action (3) failed: -110
May 9 17:11:49 olivier-desktop kernel: [12935.927420] Freezing user space
processes ... (elapsed 0.003 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.931100] OOM killer disabled.
May 9 17:11:49 olivier-desktop kernel: [12935.931101] Freezing remaining
freezable tasks ... (elapsed 0.001 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.932442] printk: Suspending
console(s) (use no_console_suspend to debug)
May 9 17:11:49 olivier-desktop kernel: [12935.933372] nuvoton-cir 00:01:
disabled
May 9 17:11:49 olivier-desktop kernel: [12935.933511] e1000e: EEE TX LPI
TIMER: 0011
[...]
May 9 17:11:49 olivier-desktop ModemManager[753]: [sleep-monitor]
system is resuming
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.4217]
manager: sleep: wake requested (sleeping: yes enabled: yes)
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.4218]
device (enp0s25): state change: activated -> unmanaged (reas
on 'sleeping', sys-iface-state: 'managed')
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.]
dhcp4 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.]
dhcp4 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.4445]
dhcp4 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.4448]
dhcp6 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.4448]
dhcp6 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.4448]
dhcp6 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 192.168.1.39 on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast group
on interface enp0s25.IPv4 with address 192.168.1.39.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv4 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:5c93:eaf1:5741:587a on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast group
on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:5
c93:eaf1:5741:587a.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Joining mDNS multicast group
on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset search domain list.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client set
default route setting: no
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset DNS server list.
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.4638]
manager: NetworkManager state is now CONNECTED_GLOBAL
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv6 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast group
on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop kernel: [12936.658740] e1000e :00:19.0
enp0s25: NIC Link is Down
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:ce9a:6874:2c00:f41c on enp0s25.
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.5495]
manager: NetworkManager state is now DISCONNECTED
May 9 17:11:49 olivier-desktop NetworkManager[644]: [1652109109.5520]
device (enp0s25): state change: unmanaged -> unavailable (re
ason 'managed', sys-iface-state: 'external')
[...]
May 9 17:11:51 olivier-desktop ModemManager[753]: [base-manager]
couldn't check support for device '/sys/devices/pci:00/:0
0:1c.3/:02:00.0': not supported by any plugin
May 9 17:11:52 olivier-desktop kernel: [12939.694959] e1000e :00:19.0
enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/
Tx
May 9 17:11:52 olivier-desktop kernel: [12939.695006] IPv6:
ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready
May 9 17:11:52 olivier-desktop NetworkManager[644]: [1652109112.5838]
device (enp0s25): carrier: link connected
May 9 17:11:52 olivier-desktop NetworkManager[644]:
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
@Sebastian adding both the kernel parameter and the two lines in the nvidia module conf file works for "systemctl suspend" - the machine can now resume OK when on wayland. Curiously though, when I try systemctl suspend-then-hibernate (my default way of suspending), I get the following in dmesg: NVRM: GPU :02:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README. and suspend does not work (I get a login prompt) Note that "systemctl hibernate" works fine on wayland and Xorg. Also, on xorg, systemctl suspend-then-hibernate also works fine. Could this be a bug on systemd? -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1
[Desktop-packages] [Bug 1970408] Re: brltty package disconnecting ttyUSB0 used for Arduino
This is currently preventing me from using a Digirig Mobile amatuer radio interface device, which uses the 10c4:ea60 Silicon Labs CP210x UART Bridge. Pop_OS depends on brltty so I can't remove the package. However, I was able to follow comment #2: Edit /etc/brltty.conf, and add line: ``` braille-device usb:: ``` This points brltty as a particular nonexistent device and prevents it from trying to take over the USB serial device. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1970408 Title: brltty package disconnecting ttyUSB0 used for Arduino Status in brltty package in Ubuntu: Confirmed Bug description: Hello I connected an ESP8266 microcontroller to my pc to use with Arduino. However, the interface didn't appears to list ttyUSB0. Upon inspection with dmesg, I noticed that the device is recognised but then brltty appears to disconnect it. [Tue Apr 26 19:09:35 2022] usb 1-8: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [Tue Apr 26 19:09:35 2022] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [Tue Apr 26 19:09:35 2022] usb 1-8: Product: CP2102 USB to UART Bridge Controller [Tue Apr 26 19:09:35 2022] usb 1-8: Manufacturer: Silicon Labs [Tue Apr 26 19:09:35 2022] usb 1-8: SerialNumber: 0001 [Tue Apr 26 19:09:35 2022] cp210x 1-8:1.0: cp210x converter detected [Tue Apr 26 19:09:35 2022] usb 1-8: cp210x converter now attached to ttyUSB0 [Tue Apr 26 19:09:38 2022] usb 1-8: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [Tue Apr 26 19:09:38 2022] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [Tue Apr 26 19:09:38 2022] cp210x 1-8:1.0: device disconnected This also appears to have happended to other people: https://stackoverflow.com/questions/52143723/usb-serial-loses- connection-immediately-in-new-linux-kernel-4-12-14 Once the brltty package is removed, the USB device mounts fine and Arduino find it (same dmesg as above, without the last 3 lines). I'm actually not sure why this package is installed as I deleted it without having to remove ubuntu-desktop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 19:15:04 2022 InstallationDate: Installed on 2022-04-06 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: brltty UpgradeStatus: Upgraded to jammy on 2022-04-18 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1970408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971195] Re: gnome-remote-desktop leads to a session crash inside qemu with virtio-vga
** Also affects: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bicha (jbicha) ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: New => Triaged ** Changed in: gnome-remote-desktop (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1971195 Title: gnome-remote-desktop leads to a session crash inside qemu with virtio- vga Status in gnome-remote-desktop package in Ubuntu: Fix Committed Status in gnome-remote-desktop source package in Jammy: Triaged Bug description: Steps to reproduce: 1. On a jammy host, create a jammy guest: $ qemu-img create -f qcow2 vm.qcow2 50G $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO] 2. Install Ubuntu in that VM (minimal install), no problems are expected yet. 3. After the installation is concluded and the VM reboots, try to login using the Wayland session (it should be the default, no need to select anything). It will fail and bring you back to the login screen (apparently due to a gnome-shell crash; I don't think the details are relevant to the problem here). What is expected: that both the Wayland and X11 sessions work out-of- the-box. Workaround: remove gnome-remote-desktop, and the Wayland session will work just fine in the conditions described above. This is why I'm reporting this issue in gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be wrong though... Extra information: 1. gnome-shell starts as expected if the X11 session is selected instead. 2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it work in both the X11 and Wayland sessions: $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971195] Re: gnome-remote-desktop leads to a session crash inside qemu with virtio-vga
The only line in the journal to mention gnome-remote-desktop is gnome-remote-desktop-daemon: libEGL warning: DRI2: failed to create dri screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1971195 Title: gnome-remote-desktop leads to a session crash inside qemu with virtio- vga Status in gnome-remote-desktop package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. On a jammy host, create a jammy guest: $ qemu-img create -f qcow2 vm.qcow2 50G $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO] 2. Install Ubuntu in that VM (minimal install), no problems are expected yet. 3. After the installation is concluded and the VM reboots, try to login using the Wayland session (it should be the default, no need to select anything). It will fail and bring you back to the login screen (apparently due to a gnome-shell crash; I don't think the details are relevant to the problem here). What is expected: that both the Wayland and X11 sessions work out-of- the-box. Workaround: remove gnome-remote-desktop, and the Wayland session will work just fine in the conditions described above. This is why I'm reporting this issue in gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be wrong though... Extra information: 1. gnome-shell starts as expected if the X11 session is selected instead. 2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it work in both the X11 and Wayland sessions: $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971195] Re: gnome-remote-desktop leads to a session crash inside qemu with virtio-vga
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1971195 Title: gnome-remote-desktop leads to a session crash inside qemu with virtio- vga Status in gnome-remote-desktop package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. On a jammy host, create a jammy guest: $ qemu-img create -f qcow2 vm.qcow2 50G $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO] 2. Install Ubuntu in that VM (minimal install), no problems are expected yet. 3. After the installation is concluded and the VM reboots, try to login using the Wayland session (it should be the default, no need to select anything). It will fail and bring you back to the login screen (apparently due to a gnome-shell crash; I don't think the details are relevant to the problem here). What is expected: that both the Wayland and X11 sessions work out-of- the-box. Workaround: remove gnome-remote-desktop, and the Wayland session will work just fine in the conditions described above. This is why I'm reporting this issue in gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be wrong though... Extra information: 1. gnome-shell starts as expected if the X11 session is selected instead. 2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it work in both the X11 and Wayland sessions: $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971195] Re: gnome-remote-desktop leads to a session crash inside qemu with virtio-vga
** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971195/+attachment/5587907/+files/journal.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1971195 Title: gnome-remote-desktop leads to a session crash inside qemu with virtio- vga Status in gnome-remote-desktop package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. On a jammy host, create a jammy guest: $ qemu-img create -f qcow2 vm.qcow2 50G $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO] 2. Install Ubuntu in that VM (minimal install), no problems are expected yet. 3. After the installation is concluded and the VM reboots, try to login using the Wayland session (it should be the default, no need to select anything). It will fail and bring you back to the login screen (apparently due to a gnome-shell crash; I don't think the details are relevant to the problem here). What is expected: that both the Wayland and X11 sessions work out-of- the-box. Workaround: remove gnome-remote-desktop, and the Wayland session will work just fine in the conditions described above. This is why I'm reporting this issue in gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be wrong though... Extra information: 1. gnome-shell starts as expected if the X11 session is selected instead. 2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it work in both the X11 and Wayland sessions: $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental
We do not want policykit to use the unmaintainable mozjs backend. That would be a hard NACK from the Security Team. The duktape backend has been merged upstream. So in order to sync this to Ubuntu, the following must be done: 1- Get Debian to switch to the duktape backend 2- Get Debian to transition all packages in the archive from PKLA policy files to JS policy files 3- Transition Ubuntu packages not in Debian from PKLA policy files to JS policy files 4- Investigate Snap policykit support, and if required, transition Snaps from PKLA policy files to JS policy files. Once the transition has been done for all software, policykit can be switched to the duktape policykit backend by syncing the package from Debian. Hopefully at that point it will be in Unstable, and not in experimental. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 0.120-6 (main) from Debian experimental Changelog entries since current kinetic version 0.105-33: https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6 In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. It appears the Debian maintainer is considering switching Debian to the updated version in time for the next Debian Stable release (so uploading to unstable later this year). My requested deadline is August 25, Ubuntu 22.10 Feature Freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
> I wondered if perhaps it this only works on some APs? That is the impression that I get, the country code info is part of the management frames transmitted by the AP, could be unsupported, not configured, or mis-configured. grep wpa may6.txt May 6 09:04:57 box wpa_supplicant[810]: wlan0: WPS-PBC-ACTIVE May 6 09:05:34 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'BELL188' May 6 09:05:36 box wpa_supplicant[810]: wlan0: Associated with 2c:79:d7:05:5e:0e May 6 09:05:36 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 6 09:05:36 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA May 6 09:05:45 box wpa_supplicant[810]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:79:d7:05:5e:0e reason=15 May 6 09:05:45 box wpa_supplicant[810]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 6 09:05:45 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="BELL188" auth_failures=1 duration=10 reason=WRONG_KEY May 6 09:05:45 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 6 09:05:45 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US May 6 09:06:58 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'BELL188' May 6 09:07:01 box wpa_supplicant[810]: wlan0: Associated with 2c:79:d7:05:5e:0e May 6 09:07:01 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 6 09:07:01 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA May 6 09:07:10 box wpa_supplicant[810]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:79:d7:05:5e:0e reason=15 May 6 09:07:10 box wpa_supplicant[810]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 6 09:07:10 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="BELL188" auth_failures=1 duration=10 reason=WRONG_KEY May 6 09:07:10 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 6 09:07:10 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US May 6 09:07:32 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'BELL188' May 6 09:07:35 box wpa_supplicant[810]: wlan0: Associated with 2c:79:d7:05:5e:0e May 6 09:07:35 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 6 09:07:35 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA May 6 09:07:44 box wpa_supplicant[810]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:79:d7:05:5e:0e reason=15 May 6 09:07:44 box wpa_supplicant[810]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 6 09:07:44 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="BELL188" auth_failures=1 duration=10 reason=WRONG_KEY May 6 09:07:44 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 6 09:07:44 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US May 6 09:08:10 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'BELL188' May 6 09:08:13 box wpa_supplicant[810]: wlan0: Associated with 2c:79:d7:05:5e:0e May 6 09:08:13 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 6 09:08:13 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA May 6 09:08:21 box wpa_supplicant[810]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:79:d7:05:5e:0e reason=3 locally_generated=1 May 6 09:08:21 box wpa_supplicant[810]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 6 09:08:21 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="BELL188" auth_failures=1 duration=10 reason=WRONG_KEY May 6 09:08:21 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 6 09:08:21 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US May 6 09:08:28 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'BELL188' May 6 09:08:31 box wpa_supplicant[810]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:79:d7:05:5e:0e reason=3 locally_generated=1 May 6 09:08:31 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 6 09:08:31 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US May 6 09:09:08 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'SHAW-DB6690' May 6 09:09:11 box wpa_supplicant[810]: wlan0: Associated with 00:fc:8d:db:66:98 May 6 09:09:11 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 6 09:09:11 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US May 6 09:09:11 box wpa_supplicant[810]: wlan0: WPA: Key negotiation completed with 00:fc:8d:db:66:98 [PTK=CCMP
[Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center
upstream report for reference was https://gitlab.gnome.org/GNOME/gnome- control-center/-/issues/1813 Unsure if xinerama is creating any issue there, could you add your /var/log/Xorg.0.log to the report? ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1813 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1813 -- 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/1972037 Title: Stack Overflow - gnome-control-center Status in gnome-control-center package in Ubuntu: New Bug description: Program: gnome-control-center Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) OS: ubuntu 20.04.4 LTS GNOME Version: 3.36.8 (ubuntu default download) Windowing System: X11 Graphics: GeForce 8400GS/PCIe/SSE2 Driver: Using NVIDIA binary driver version 340.108 Source: download version from ubuntu Steps to reproduce: Reset GNOME settings with: dconf reset -f /org/gnome/control-center/ Open GNOME Settings with: /usr/bin/gnome-control-center Click on "Displays" and receive: Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Segmentation fault (core dumped) Repeated using gdb with package symbols. Output of "bt -full" in attachment (with a few comments). (Submitted to gnome.org, but they said it is out of date and not supported by them.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 6 20:38:55 2022 InstallationDate: Installed on 2011-07-11 (3952 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New -- 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/1972037 Title: Stack Overflow - gnome-control-center Status in gnome-control-center package in Ubuntu: New Bug description: Program: gnome-control-center Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) OS: ubuntu 20.04.4 LTS GNOME Version: 3.36.8 (ubuntu default download) Windowing System: X11 Graphics: GeForce 8400GS/PCIe/SSE2 Driver: Using NVIDIA binary driver version 340.108 Source: download version from ubuntu Steps to reproduce: Reset GNOME settings with: dconf reset -f /org/gnome/control-center/ Open GNOME Settings with: /usr/bin/gnome-control-center Click on "Displays" and receive: Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Segmentation fault (core dumped) Repeated using gdb with package symbols. Output of "bt -full" in attachment (with a few comments). (Submitted to gnome.org, but they said it is out of date and not supported by them.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 6 20:38:55 2022 InstallationDate: Installed on 2011-07-11 (3952 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
@Dustin, could you do a new report using $ ubuntu-bug wpasupplicant ? then edit /lib/systemd/system/wpa_supplicant.service to add a '-d' to the ExecStart cmd, restart the system, trigger the bug and add the journal log $ journalctl -b 0 > log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: Fix Released Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center
two HDMI screens side-by-side 2 old nvidia cards (both GeForce 8400GS) nvidia driver 340.108 (latest version, required by cards) Xinerama enabled software kept fully up-to-date with stable release Side comment -- gnome seems to crash a lot. This is first situation where I can use gdb to get stack information. On Mon, May 9, 2022 at 9:41 AM Sebastien Bacher <1972...@bugs.launchpad.net> wrote: > just verbal description of the numbers of screens, layout, video > cards/drivers > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1972037 > > Title: > Stack Overflow - gnome-control-center > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > > Program: gnome-control-center > Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) > OS: ubuntu 20.04.4 LTS > GNOME Version: 3.36.8 (ubuntu default download) > Windowing System: X11 > Graphics: GeForce 8400GS/PCIe/SSE2 > Driver: Using NVIDIA binary driver version 340.108 > Source: download version from ubuntu > > Steps to reproduce: > > Reset GNOME settings with: > dconf reset -f /org/gnome/control-center/ > Open GNOME Settings with: > /usr/bin/gnome-control-center > Click on "Displays" and receive: > Xlib: extension "RANDR" missing on display ":0". > Xlib: extension "RANDR" missing on display ":0". > Segmentation fault (core dumped) > > Repeated using gdb with package symbols. > Output of "bt -full" in attachment (with a few comments). > > (Submitted to gnome.org, but they said it is out of date and not > supported by them.) > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-control-center 1:3.36.5-0ubuntu4 > ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 > Uname: Linux 5.4.0-100-generic x86_64 > NonfreeKernelModules: nvidia > ApportVersion: 2.20.11-0ubuntu27.23 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: GNOME-Flashback:GNOME > Date: Fri May 6 20:38:55 2022 > InstallationDate: Installed on 2011-07-11 (3952 days ago) > InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 > (20110426) > SourcePackage: gnome-control-center > UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions > > -- 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/1972037 Title: Stack Overflow - gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Program: gnome-control-center Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) OS: ubuntu 20.04.4 LTS GNOME Version: 3.36.8 (ubuntu default download) Windowing System: X11 Graphics: GeForce 8400GS/PCIe/SSE2 Driver: Using NVIDIA binary driver version 340.108 Source: download version from ubuntu Steps to reproduce: Reset GNOME settings with: dconf reset -f /org/gnome/control-center/ Open GNOME Settings with: /usr/bin/gnome-control-center Click on "Displays" and receive: Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Segmentation fault (core dumped) Repeated using gdb with package symbols. Output of "bt -full" in attachment (with a few comments). (Submitted to gnome.org, but they said it is out of date and not supported by them.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 6 20:38:55 2022 InstallationDate: Installed on 2011-07-11 (3952 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971089] Re: Network Manager bug constant reconnecting and CPU usage
** Changed in: network-manager (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/1971089 Title: Network Manager bug constant reconnecting and CPU usage Status in network-manager package in Ubuntu: New Bug description: Anyconnectin result cpu heavy usage. constant reconnections wifi/ethernet..no matter ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun May 1 17:00:00 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-03 (1793 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.148 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to jammy on 2022-04-25 (6 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
I'm not sure if we have the same issue or better if the bug has the same cause. We installed a ubuntu 22.04 and added a hotspot via nmcli. The hotspot is visible, but we can't connect with any devices. As soon we change the security from "WPA & WPA2" to "None" we can connect without any issues. If we choose "WPA3 Personal" we get the error message that the password is invalid (which is not the case). With 20.04 it works fine (because it still use 2.9-1ubuntu4.3)! Is there any ETA for the new (fixed) version ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: Fix Released Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972654] [NEW] [security review] Sync policykit-1 0.120-6 (main) from Debian experimental
*** This bug is a security vulnerability *** Public security bug reported: Please sync policykit-1 0.120-6 (main) from Debian experimental Changelog entries since current kinetic version 0.105-33: https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6 In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. It appears the Debian maintainer is considering switching Debian to the updated version in time for the next Debian Stable release (so uploading to unstable later this year). My requested deadline is August 25, Ubuntu 22.10 Feature Freeze. ** Affects: policykit-1 (Ubuntu) Importance: Medium Assignee: Ubuntu Security Team (ubuntu-security) Status: Confirmed ** Tags: kinetic ** Changed in: policykit-1 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: policykit-1 (Ubuntu) Status: New => Confirmed ** Summary changed: - Sync policykit-1 0.120-6 (main) from Debian experimental + [security review] Sync policykit-1 0.120-6 (main) from Debian experimental ** Changed in: policykit-1 (Ubuntu) Importance: Wishlist => Medium ** Changed in: policykit-1 (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) ** Tags added: kinetic ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 0.120-6 (main) from Debian experimental Changelog entries since current kinetic version 0.105-33: https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6 In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. It appears the Debian maintainer is considering switching Debian to the updated version in time for the next Debian Stable release (so uploading to unstable later this year). My requested deadline is August 25, Ubuntu 22.10 Feature Freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center
just verbal description of the numbers of screens, layout, video cards/drivers -- 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/1972037 Title: Stack Overflow - gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Program: gnome-control-center Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) OS: ubuntu 20.04.4 LTS GNOME Version: 3.36.8 (ubuntu default download) Windowing System: X11 Graphics: GeForce 8400GS/PCIe/SSE2 Driver: Using NVIDIA binary driver version 340.108 Source: download version from ubuntu Steps to reproduce: Reset GNOME settings with: dconf reset -f /org/gnome/control-center/ Open GNOME Settings with: /usr/bin/gnome-control-center Click on "Displays" and receive: Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Segmentation fault (core dumped) Repeated using gdb with package symbols. Output of "bt -full" in attachment (with a few comments). (Submitted to gnome.org, but they said it is out of date and not supported by them.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 6 20:38:55 2022 InstallationDate: Installed on 2011-07-11 (3952 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Try nvidia.NVreg_PreserveVideoMemoryAllocations=1 as suggested by @vanvugt You may wanna change the file path of the temporary file thought for better performance. -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2
[Desktop-packages] [Bug 1968588] Re: Cannot create or add VPN in connection editor
** Tags added: desktop-lts-wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1968588 Title: Cannot create or add VPN in connection editor Status in Network Manager Applet: Unknown Status in network-manager-applet package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: In 22.04 I am unable to create a new VPN in network manager and nm- connection-editor. After filing in the entire form the save button remains disabled! watching the terminal provides this error: Cannot save connection due to error: Invalid setting General: connection.interface-name: '': interface name must not be empty Seems like the form validator is not looking at the right field! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-gnome 1.24.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 10:49:34 2022 ExecutablePath: /usr/bin/nm-connection-editor InstallationDate: Installed on 2022-04-09 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 IwConfig: lono wireless extensions. enp0s3no wireless extensions. ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RfKill: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 31e61843-ef5f-31e8-96a2-cf86d47e015c ethernet 1649688323 Mon 11 Apr 2022 10:45:23 AM EDT yes -999 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s3 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s3 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 31e61843-ef5f-31e8-96a2-cf86d47e015c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1968588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971076] Re: 2.36 doesn't work with orca anymore
Could you perhaps report the issue directly upstream on https://gitlab.gnome.org/GNOME/orca/-/issues ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1971076 Title: 2.36 doesn't work with orca anymore Status in webkit2gtk package in Ubuntu: Incomplete Bug description: Since Ubuntu 22.04 I can not read the content of the yelp pages, le content of a mail from evolution or a web page from epiphany. This worked correctly for Ubuntu 21.10 or Ubuntu 20.04 LTS. This problem occurs if I migrate from a previous version, or if I reinstall from scrash. Is there a new setting that I don't aware of? This also could be related to webkitgtk I suppose. A work arround is to select all the texte and to copy it to a place that I can read (gedit). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: orca 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun May 1 10:03:38 2022 InstallationDate: Installed on 2022-04-03 (27 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: orca UpgradeStatus: Upgraded to jammy on 2022-04-12 (18 days ago) mtime.conffile..etc.xdg.autostart.orca-autostart.desktop: 2022-04-17T10:13:33.207956 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1971076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center
Would be happy to. What files would you most like to see? On Mon, May 9, 2022 at 4:46 AM Sebastien Bacher <1972...@bugs.launchpad.net> wrote: > could you provide some details on the screens configuration you are > using? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1972037 > > Title: > Stack Overflow - gnome-control-center > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > > Program: gnome-control-center > Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) > OS: ubuntu 20.04.4 LTS > GNOME Version: 3.36.8 (ubuntu default download) > Windowing System: X11 > Graphics: GeForce 8400GS/PCIe/SSE2 > Driver: Using NVIDIA binary driver version 340.108 > Source: download version from ubuntu > > Steps to reproduce: > > Reset GNOME settings with: > dconf reset -f /org/gnome/control-center/ > Open GNOME Settings with: > /usr/bin/gnome-control-center > Click on "Displays" and receive: > Xlib: extension "RANDR" missing on display ":0". > Xlib: extension "RANDR" missing on display ":0". > Segmentation fault (core dumped) > > Repeated using gdb with package symbols. > Output of "bt -full" in attachment (with a few comments). > > (Submitted to gnome.org, but they said it is out of date and not > supported by them.) > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-control-center 1:3.36.5-0ubuntu4 > ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 > Uname: Linux 5.4.0-100-generic x86_64 > NonfreeKernelModules: nvidia > ApportVersion: 2.20.11-0ubuntu27.23 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: GNOME-Flashback:GNOME > Date: Fri May 6 20:38:55 2022 > InstallationDate: Installed on 2011-07-11 (3952 days ago) > InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 > (20110426) > SourcePackage: gnome-control-center > UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions > > -- 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/1972037 Title: Stack Overflow - gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Program: gnome-control-center Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) OS: ubuntu 20.04.4 LTS GNOME Version: 3.36.8 (ubuntu default download) Windowing System: X11 Graphics: GeForce 8400GS/PCIe/SSE2 Driver: Using NVIDIA binary driver version 340.108 Source: download version from ubuntu Steps to reproduce: Reset GNOME settings with: dconf reset -f /org/gnome/control-center/ Open GNOME Settings with: /usr/bin/gnome-control-center Click on "Displays" and receive: Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Segmentation fault (core dumped) Repeated using gdb with package symbols. Output of "bt -full" in attachment (with a few comments). (Submitted to gnome.org, but they said it is out of date and not supported by them.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 6 20:38:55 2022 InstallationDate: Installed on 2011-07-11 (3952 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
** Changed in: evince (Ubuntu) Status: Incomplete => New -- 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/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: New Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972070] Re: gdk-pixbuf does not support saving as gif
Thank you for your bug report, indeed and that's probably an upstream issue worth reporting on https://gitlab.gnome.org/GNOME/gdk- pixbuf/-/issues ** Changed in: gdk-pixbuf (Ubuntu) Importance: Undecided => Low ** Changed in: gdk-pixbuf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1972070 Title: gdk-pixbuf does not support saving as gif Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: Hello, I'm getting this message then I try to save a rotated GIF image in Image Viewer: "This build of gdk-pixbuf does not support saving the image format: gif" Description: Ubuntu 22.04 LTS Release: 22.04 libgdk-pixbuf-2.0-0: Installed: 2.42.8+dfsg-1 Candidate: 2.42.8+dfsg-1 Version table: *** 2.42.8+dfsg-1 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1972070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Unfortunately nvidia.NVreg_EnableS0ixPowerManagement=1 did not work on an old Asus Rog Maximus VIII mobo (Kabylake), nvidia 1650. I also tried this: /etc/modprobe.d/nvidia-power-management.conf options nvidia NVreg_PreserveVideoMemoryAllocations=1 and it didn't work either. Missing textures after suspend. Any other hint? -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku:
[Desktop-packages] [Bug 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)
(And Firefox gave me a notification about hitting version 100, so it presumably did update) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1972545 Title: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I am using the Firefox Snap on a fresh install of 22.04 (using defaults, as far as I know). Normally, Firefox shows an indicator in the Dock showing that it is running (the orange dot) and gives the ability to choose between open windows. At the moment, I have Firefox windows open, but nothing is shown in the Dock (as if it is closed). My suspicion is that the snap was refreshed while running and this confused Gnome Shell. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 13:31:40 2022 InstallationDate: Installed on 2022-04-24 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)
** Attachment added: "As expected, closing and reopening Firefox makes it work as expected" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587903/+files/Screenshot%20from%202022-05-09%2013-44-45.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1972545 Title: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I am using the Firefox Snap on a fresh install of 22.04 (using defaults, as far as I know). Normally, Firefox shows an indicator in the Dock showing that it is running (the orange dot) and gives the ability to choose between open windows. At the moment, I have Firefox windows open, but nothing is shown in the Dock (as if it is closed). My suspicion is that the snap was refreshed while running and this confused Gnome Shell. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 13:31:40 2022 InstallationDate: Installed on 2022-04-24 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)
** Attachment added: "Screenshot of the dock" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587901/+files/Screenshot%20from%202022-05-09%2013-32-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1972545 Title: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I am using the Firefox Snap on a fresh install of 22.04 (using defaults, as far as I know). Normally, Firefox shows an indicator in the Dock showing that it is running (the orange dot) and gives the ability to choose between open windows. At the moment, I have Firefox windows open, but nothing is shown in the Dock (as if it is closed). My suspicion is that the snap was refreshed while running and this confused Gnome Shell. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 13:31:40 2022 InstallationDate: Installed on 2022-04-24 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972545] [NEW] Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)
Public bug reported: I am using the Firefox Snap on a fresh install of 22.04 (using defaults, as far as I know). Normally, Firefox shows an indicator in the Dock showing that it is running (the orange dot) and gives the ability to choose between open windows. At the moment, I have Firefox windows open, but nothing is shown in the Dock (as if it is closed). My suspicion is that the snap was refreshed while running and this confused Gnome Shell. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 13:31:40 2022 InstallationDate: Installed on 2022-04-24 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "journalctl -b 0 > log" https://bugs.launchpad.net/bugs/1972545/+attachment/5587897/+files/log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1972545 Title: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I am using the Firefox Snap on a fresh install of 22.04 (using defaults, as far as I know). Normally, Firefox shows an indicator in the Dock showing that it is running (the orange dot) and gives the ability to choose between open windows. At the moment, I have Firefox windows open, but nothing is shown in the Dock (as if it is closed). My suspicion is that the snap was refreshed while running and this confused Gnome Shell. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 13:31:40 2022 InstallationDate: Installed on 2022-04-24 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971168] Re: [snap] Downloaded files not saved when saving to local network share
I've updated the bug to reflect that multiple applications are affected by this. On my system I can reproduce the issue with Firefox and Chromium, both installed via snap. ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Description changed: Steps to reproduce: - 1. Run Firefox as a Snap package in Ubuntu 22.04 + 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable - 4. Open any website containing images in Firefox + 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share + * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. ** Summary changed: - [snap] Downloaded files not saved when saving to local network share + [snap] Files on local network shares are not opened / written -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972059] Re: One screen does not come back from lock
Still on wayland ** Attachment added: "journalctl -b0 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+attachment/5587892/+files/journal.zip -- 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/1972059 Title: One screen does not come back from lock Status in mutter package in Ubuntu: Incomplete Bug description: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972120] Re: Ubuntu 22.04 stuck
Determining whether a bug report is actually a support request can be quite challenging, but if you decide the bug is a support request you can convert it to such by clicking "Convert to a question" at the top of the bug's web page. This will mark the bug as "Invalid", create a new question in the answer tracker and link it to the bug. In the comment dialog that you receive, post a comment to inform the reporter about your action, and advise them to use the support tracker for any future problems. Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. It is also a good idea to change the source package beforehand if it's set incorrectly, so that the question will be associated with the correct package in the answer tracker, or edit the question afterwards and assign it to the correct package. If it doesn't pertain to a specific package, change it to "Ubuntu". ** Changed in: xdg-desktop-portal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1972120 Title: Ubuntu 22.04 stuck Status in xdg-desktop-portal package in Ubuntu: Invalid Bug description: To my simplest knowledge I think my desktop is infected.furst I was using Ubuntu 18.04 and I had issues with Firefox I tried another browser and it works ,then as I was not satisfied I upgraded to Ubuntu 20.04 and the problem worsened,then I upgraded to 22.04 for mor than week.at first it sticks at the stars then now I came to have the machin working but in the moment I open any app it sticks therefore I can't use my computer. I hope to receive some help to get back my desktop thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1972120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972125] Re: Remmina caches fingerprints wrongly when using two profiles with SSH tunneling
Thank you for your bug report. We don't have an active maintainer working on remmina so since you seem to already know your way around upstream you might want to also report the issue directly to gitlab -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1972125 Title: Remmina caches fingerprints wrongly when using two profiles with SSH tunneling Status in remmina package in Ubuntu: New Bug description: When using two profiles and alternating between connecting to them, it always prompts that the certificate has changed and the old fingerprint is the fingerprint for the other profile. I suspect that this is because I use SSH tunneling for both and Remmina is caching the fingerprints under the SSH tunnel for localhost. (Also, the "tunneling via loopback address" feature is undocumented. Should I open another bug for that?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1972125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972123] Re: Online accounts crashes on sign in
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => High ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1972123 Title: Online accounts crashes on sign in Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: I noticed that my to-dos weren't syncing, so I checked online accounts and there's this triangle warning icon. I click into it and it says "Credentials have expired", "Sign in to enable this account." Now when I click "Sign in", the pop up changes to a frozen progress bar on top and with empty content, then crashes after a few seconds. Now I can't sync anything and can't fix it. Ubuntu 22.04 LTS, Wayland on Nvidia 510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1972123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: File dialog not displayed within screen range
BTW this is not only in gedit, also in other apps. -- 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/1972151 Title: File dialog not displayed within screen range Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972127] Re: gnome-todo change date function is cumbersome
Thank you for your bug report. Confirming the issue, it does sound similar to https://gitlab.gnome.org/GNOME/gnome-todo/-/issues/218 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-todo/-/issues #218 https://gitlab.gnome.org/GNOME/gnome-todo/-/issues/218 ** Changed in: gnome-todo (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-todo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-todo in Ubuntu. https://bugs.launchpad.net/bugs/1972127 Title: gnome-todo change date function is cumbersome Status in gnome-todo package in Ubuntu: Confirmed Bug description: When I change the due date to a date in another month in the "Today" view, the item immediately disappears right as I click the right arrow on the month. I have to go to scheduled, scroll all the way down, find the task in hundreds of other tasks, then change the date to the actual day. I sometimes forget to do that and miss my actual task due date. It should only update the month in the date selection UI, and not actually update until a day is selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-todo/+bug/1972127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972129] Re: user account show different users than "Users and Groups"
Thank you for your bug report. It sounds a bit similar to bug #1971559 The reason it displayed the wizard to create a first user is because it didn't recognize your existing account. Could you to do # /usr/libexec/accounts-daemon --debug and see what that does display about your account? also does /var/lib/AccountsService/users/$USER includes a SystemAccount=true key? ** Package changed: ubuntu-release-upgrader (Ubuntu) => accountsservice (Ubuntu) ** Changed in: accountsservice (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1972129 Title: user account show different users than "Users and Groups" Status in accountsservice package in Ubuntu: Incomplete Bug description: upgraded from 21.10 to 22.04. Upgrade seemed to require creating a new (admin) id, which I did. When I now login the new account name is displayed but I have to list other users to be able to login with my pre-upgrade account. Going to system settings -> User Accounts shows only the new account. Once logged in, invoking "Users & Groups" shows both new id and pre-upgrade user account. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 8 16:30:27 2022 InstallationDate: Installed on 2020-07-18 (659 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-04-29 (9 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1972129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972129] [NEW] user account show different users than "Users and Groups"
You have been subscribed to a public bug: upgraded from 21.10 to 22.04. Upgrade seemed to require creating a new (admin) id, which I did. When I now login the new account name is displayed but I have to list other users to be able to login with my pre-upgrade account. Going to system settings -> User Accounts shows only the new account. Once logged in, invoking "Users & Groups" shows both new id and pre-upgrade user account. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 8 16:30:27 2022 InstallationDate: Installed on 2020-07-18 (659 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-04-29 (9 days ago) VarLogDistupgradeTermlog: ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug dist-upgrade jammy -- user account show different users than "Users and Groups" https://bugs.launchpad.net/bugs/1972129 You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice 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 1972151] Re: File dialog not displayed within screen range
Thank you for your bug report. Could you do 'journalctl -b 0 > log' next time you get the issue and attach the file to the report? ** Package changed: gedit (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972151 Title: File dialog not displayed within screen range Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971415] Re: Remote desktop is automatically enabled after login
Debian and Ubuntu auto-enable installed systemd unit in their packages, which is different from what RH is doing. If that 's not wanted here then we should probably force disable it, as in https://launchpad.net/ubuntu/+source/gamemode/1.5.1-0ubuntu2 Note that there is still a gnome-control-center issue probably here since it should be able to override /etc/systemd/user/gnome- session.target.wants/gnome-remote-desktop.service ** Changed in: gnome-remote-desktop (Ubuntu) Importance: Undecided => High ** Changed in: gnome-remote-desktop (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1971415 Title: Remote desktop is automatically enabled after login Status in gnome-remote-desktop package in Ubuntu: New Bug description: If I disable sharing/remote desktop in GNOME Control Center, then log out and back in, it is automatically enabled again. I report this as a security vulnerability because remote desktop is enabled without the user's knowledge. Software versions: - Ubuntu 22.04 - gnome-remote-desktop 42.0-4ubuntu1 - gnome-control-center 1:41.4-1ubuntu13 Steps to reproduce: 1. Start with Remote Desktop enabled. "systemctl --user status gnome-remote-desktop.service" reports "active (running)". 2. Disable Remote Desktop in Control Center. systemctl reports "inactive (dead)". 3. Log out and back in. 4. Open Control Center. Remote Desktop is enabled again. systemctl reports "active (running)". Expected behavior: Remote Desktop should stay disabled upon the new login. Actual behavior: Remote Desktop was automatically enabled again. Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1775#note_1443319 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
I'm using a RTX 3080 Ti on a Z690 Desktop motherboard and enabling the S0ix option fixed the problem for me. I've added the following option "nvidia.NVreg_EnableS0ixPowerManagement=1" to GRUB_CMDLINE_LINUX_DEFAULT. -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd.
[Desktop-packages] [Bug 1853007]
This still appears to be an issue on Windows and also Linux. Folders such as pid-32601 get created when you open an attachment. The number changes each time you open a new session of Thunderbird, but the folders and their contents are never cleared. -- 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/1853007 Title: nsemail and nscopy files left in /tmp Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Triaged Bug description: thunderbird leaves nsemail and nscopy files in /tmp: # ls -l /tmp/ns* -rw--- 1 alistair alistair 5522 Nov 18 08:42 /tmp/nscopy-1.tmp -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nscopy-2.tmp -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nscopy-3.tmp -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nscopy.tmp -rw--- 1 alistair alistair 25790 Nov 15 09:26 /tmp/nsemail-10.eml -rw--- 1 alistair alistair 5840 Nov 15 09:28 /tmp/nsemail-11.eml -rw--- 1 alistair alistair 25442 Nov 15 09:29 /tmp/nsemail-12.eml -rw--- 1 alistair alistair 2838 Nov 15 09:29 /tmp/nsemail-13.eml -rw--- 1 alistair alistair 8556 Nov 15 10:10 /tmp/nsemail-14.eml -rw--- 1 alistair alistair 1659 Nov 15 10:32 /tmp/nsemail-15.eml -rw--- 1 alistair alistair 3240 Nov 15 10:47 /tmp/nsemail-16.eml -rw--- 1 alistair alistair 3260 Nov 15 10:57 /tmp/nsemail-17.eml -rw--- 1 alistair alistair 107975 Nov 15 13:43 /tmp/nsemail-18.eml -rw--- 1 alistair alistair 4878 Nov 15 13:44 /tmp/nsemail-19.eml -rw--- 1 alistair alistair 21150 Nov 13 08:43 /tmp/nsemail-1.eml -rw--- 1 alistair alistair 2974 Nov 18 08:41 /tmp/nsemail-1.html -rw--- 1 alistair alistair 6328 Nov 15 13:45 /tmp/nsemail-20.eml -rw--- 1 alistair alistair 134689 Nov 15 13:49 /tmp/nsemail-21.eml -rw--- 1 alistair alistair 2733 Nov 15 17:15 /tmp/nsemail-22.eml -rw--- 1 alistair alistair 53857 Nov 16 09:23 /tmp/nsemail-23.eml -rw--- 1 alistair alistair 89392 Nov 16 09:39 /tmp/nsemail-24.eml -rw--- 1 alistair alistair 80120 Nov 17 10:52 /tmp/nsemail-25.eml -rw--- 1 alistair alistair 6361 Nov 17 18:45 /tmp/nsemail-26.eml -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nsemail-27.eml -rw--- 1 alistair alistair 5522 Nov 18 08:41 /tmp/nsemail-28.eml -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nsemail-29.eml -rw--- 1 alistair alistair 29937 Nov 13 09:37 /tmp/nsemail-2.eml -rw--- 1 alistair alistair 5057 Nov 18 08:43 /tmp/nsemail-2.html -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nsemail-30.eml -rw--- 1 alistair alistair 2015 Nov 13 09:40 /tmp/nsemail-3.eml -rw--- 1 alistair alistair 4949 Nov 18 08:49 /tmp/nsemail-3.html -rw--- 1 alistair alistair 183446 Nov 14 08:48 /tmp/nsemail-4.eml -rw--- 1 alistair alistair 59817 Nov 15 08:41 /tmp/nsemail-5.eml -rw--- 1 alistair alistair 9751 Nov 15 08:47 /tmp/nsemail-6.eml -rw--- 1 alistair alistair 2967 Nov 15 08:49 /tmp/nsemail-7.eml -rw--- 1 alistair alistair 2983 Nov 15 08:54 /tmp/nsemail-8.eml -rw--- 1 alistair alistair 19780 Nov 15 09:14 /tmp/nsemail-9.eml -rw--- 1 alistair alistair 27900 Nov 13 08:34 /tmp/nsemail.eml -rw--- 1 alistair alistair 1317 Nov 18 08:38 /tmp/nsemail.html -rw--- 1 alistair alistair 1115 Nov 18 08:41 /tmp/nsmail-1.tmp -rw--- 1 alistair alistair 2424 Nov 18 08:43 /tmp/nsmail-2.tmp -rw--- 1 alistair alistair 2000 Nov 18 08:49 /tmp/nsmail-3.tmp -rw--- 1 alistair alistair967 Nov 18 08:38 /tmp/nsmail.tmp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.1.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 2211 F pulseaudio BuildID: 20191010144232 Channel: Unavailable Date: Mon Nov 18 08:50:15 2019 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback dns-search integrics.com InstallationDate: Installed on 2017-08-16 (823 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 1.0.0.1 dev wlp58s0 proto dhcp metric 600 1.0.0.0/21 dev wlp58s0 proto kernel scope link src 1.0.1.146 metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 NoProfiles: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
I'm not entirely convinced NetworkManager is working correctly this regard? I *was* checking the wifi regulatory domain with "iw reg get" which consistently shows UNSET both globally and for phy#0 under the desktop for Pi images: $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (N/A, 20), (N/A) (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) phy#0 country 99: DFS-UNSET (2402 - 2482 @ 40), (6, 20), (N/A) (2474 - 2494 @ 20), (6, 20), (N/A) (5140 - 5360 @ 160), (6, 20), (N/A) (5460 - 5860 @ 160), (6, 20), (N/A) Still, perhaps "iw" doesn't know about changes that wpa_supplicant makes? On a freshly flashed jammy pi desktop card, I get the following output when looking for REGDOM in the wpa_supplicant logs: $ journalctl -u wpa_supplicant -g REGDOM -- Boot 732bf3d726d543d4985f9e8ded5b5dc3 -- May 09 11:19:54 miss-piggy wpa_supplicant[727]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD The "WORLD" region is presumably consistent with "UNSET" so it doesn't look like NetworkManager or wpa_supplicant is setting things correctly there. I wondered if perhaps it this only works on some APs? So here's the output from my regular development Pi. This also runs the jammy desktop, but it's not a freshly flashed image -- it's been upgraded thru every release since hirsute so it's probably a bit crufty -- but it has travelled with me to various places so it's seen a few different access points (it spends most of its time on ethernet at home though, so the lack of lots of REGDOM changes is not too surprising): -- Boot 3342ed4b84f14e6a8f7b900d240b2c4d -- -- Boot d9087ec569c64e258d9b0a39d5d51c81 -- -- Boot b4c27a9655d747d48fc16329f73ad596 -- -- Boot d431767f6d89494bba39cc9ab9bce969 -- Sep 29 00:09:43 kermit wpa_supplicant[1081]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD -- Boot 345a7579a52147aea56af3152178c199 -- Sep 29 09:28:02 kermit wpa_supplicant[1077]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD -- Boot 624126fce6cc45abad47cb42b9ac256f -- -- Boot e424d65195804a6eae2f948ee1e4ef38 -- -- Boot 77fb125a0ecc4df985d5317cd536b54a -- -- Boot da38e67821874b3fa66a330acf17f18c -- -- Boot 02be9377913d4886b21988b903d1b4cd -- -- Boot 8a6dc8a10b0f42689056adacb374d269 -- -- Boot 85bbc4cfc473439a899e467a2debb201 -- -- Boot fa07d0686c68401696caf2b3e4c402dd -- Jan 14 15:09:22 kermit wpa_supplicant[87530]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD -- Boot 9e7e7bf75790439bbc2e72371a14c8ab -- -- Boot a70d0f3889794224a7bf370998aaf7dd -- -- Boot bd314e15c8f1415eb75c9950129edd5b -- -- Boot c54489d0e45b4318b1b07d88bdaff7ea -- -- Boot 370a4871b0ec43f9a1b58cab78ac875c -- -- Boot 4756c93714f247009f5b93f228925455 -- -- Boot 884e307c2a13455b9fbb913e0a0f0c29 -- -- Boot bad77d689f714ca88d38f498cd8bfa2b -- -- Boot 1cf2c96be69748afa60489603ef8b771 -- -- Boot 09375e4eaaf94141a8cfe904bc303989 -- -- Boot 8fa2bdfb2e6e4ad0abeda9b3a79ac37a -- -- Boot 6c23de48f7a748d995cce77b9a908d3f -- -- Boot 364f760176b54df5b3fcaa5b978f3e70 -- -- Boot ff656412414f4c7880079f7bbf07400a -- -- Boot ebb1115d58724cf9bd544028d01c6e96 -- -- Boot 5c85c03736934ed6a2426544f5f98b88 -- -- Boot 6051d9f10827419996db1bfa376ec562 -- -- Boot 4996ddb853a248268b27e93adff373e1 -- -- Boot 0b7927e93a38434683395e88d202a8e1 -- Feb 14 09:57:26 kermit wpa_supplicant[1030]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD -- Boot 08038d28c346496eb7884859c306ca4c -- -- Boot b2c62ed0866d4618ac058670dbaae672 -- Feb 17 01:37:49 kermit wpa_supplicant[1032]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD -- Boot 5a2883f8ce074e748e9a94beaf72f123 -- -- Boot ec2157fa46fa48a3ba3445bfa7fe4b1b -- -- Boot e2dbc92b2764473eb8d65a1f7e6df5df -- -- Boot ec2157fa46fa48a3ba3445bfa7fe4b1b -- -- Boot e2dbc92b2764473eb8d65a1f7e6df5df -- -- Boot a8ef52e6c63949cea168ea8c1d06d148 -- Feb 23 10:43:59 kermit wpa_supplicant[1027]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD -- Boot 319081b9562a4c20aa1560a4fe998f19 -- -- Boot 4d3841cc1dbb4906a4465dd2122f64a8 -- Feb 26 18:18:07 kermit wpa_supplicant[1048]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=DE -- Boot 8729c7f4e1ae45dcbece9aeceb9b19cb -- -- Boot 8034051089274a34ba65bc96d749a9b7 -- -- Boot 8729c7f4e1ae45dcbece9aeceb9b19cb -- Mar 03 10:07:39 kermit wpa_supplicant[1040]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD -- Boot 8034051089274a34ba65bc96d749a9b7 -- Mar 11 11:20:39 kermit wpa_supplicant[1040]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD -- Boot dcd973755091479b9be508eaf11667dd -- -- Boot b0c3f4f9a2d64a8a959844ad1773e6c1 --
[Desktop-packages] [Bug 1972150] Re: Login screen freezes and sometimes shows artifacts
*** This bug is a duplicate of bug 1882353 *** https://bugs.launchpad.net/bugs/1882353 A new bug for that might make sense, although only really if bug 1882353 was declared fixed and your secondary issue remained. So maybe don't create a new bug just yet. ** This bug has been marked a duplicate of bug 1882353 Ubuntu Dock and Top bar accessible from lockscreen -- 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/1972150 Title: Login screen freezes and sometimes shows artifacts Status in gnome-shell package in Ubuntu: Incomplete Bug description: Sometimes when unlocking, it doesn't accept the correct password and doesn't show any errors, just keeps spinning and I have to press "escape" twice to be able to enter the password in the text box again, and this behavior keeps like that until I restart gdm from another TTY or reboot. Sometimes while switching TTY's, it shows artifacts like the screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon May 9 09:04:10 2022 InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) modified.conffile..etc.pam.d.gdm-password: [modified] mtime.conffile..etc.pam.d.gdm-password: 2022-02-19T02:26:10.814729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972150] Re: Login screen freezes and sometimes shows artifacts
I mean after entering the password and pressing enter, it just keep spinning until pressing "escape" to be able to re-enter the password again even if the password is correct, this can happen whether there is artifacts or not. May be I should create a separate bug for this? -- 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/1972150 Title: Login screen freezes and sometimes shows artifacts Status in gnome-shell package in Ubuntu: Incomplete Bug description: Sometimes when unlocking, it doesn't accept the correct password and doesn't show any errors, just keeps spinning and I have to press "escape" twice to be able to enter the password in the text box again, and this behavior keeps like that until I restart gdm from another TTY or reboot. Sometimes while switching TTY's, it shows artifacts like the screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon May 9 09:04:10 2022 InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) modified.conffile..etc.pam.d.gdm-password: [modified] mtime.conffile..etc.pam.d.gdm-password: 2022-02-19T02:26:10.814729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971415] Re: Remote desktop is automatically enabled after login
It sounds related but as far as I can tell, it is not a duplicate of [1]. I can produce the erroneous behavior with g-c-c 1:41.4-1ubuntu13 (that includes the fix for [1]). The issue boils down to this: I disable Remote Desktop in the control center. I log out and back in. Remote Desktop is enabled again (both the service and the switch in the control center). [1] https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1969619 ** This bug is no longer a duplicate of bug 1969619 RDP Sharing appears on by default in jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1971415 Title: Remote desktop is automatically enabled after login Status in gnome-remote-desktop package in Ubuntu: New Bug description: If I disable sharing/remote desktop in GNOME Control Center, then log out and back in, it is automatically enabled again. I report this as a security vulnerability because remote desktop is enabled without the user's knowledge. Software versions: - Ubuntu 22.04 - gnome-remote-desktop 42.0-4ubuntu1 - gnome-control-center 1:41.4-1ubuntu13 Steps to reproduce: 1. Start with Remote Desktop enabled. "systemctl --user status gnome-remote-desktop.service" reports "active (running)". 2. Disable Remote Desktop in Control Center. systemctl reports "inactive (dead)". 3. Log out and back in. 4. Open Control Center. Remote Desktop is enabled again. systemctl reports "active (running)". Expected behavior: Remote Desktop should stay disabled upon the new login. Actual behavior: Remote Desktop was automatically enabled again. Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1775#note_1443319 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972155] Re: [SRU] libreoffice 7.2.7 for impish
** No longer affects: libreoffice (Ubuntu) ** Changed in: libreoffice (Ubuntu Impish) Status: New => In Progress -- 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/1972155 Title: [SRU] libreoffice 7.2.7 for impish Status in libreoffice source package in Impish: In Progress Bug description: [Impact] * LibreOffice 7.2.7 is in its seventh (and last) bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release * Version 7.2.6 is currently released in impish. For a list of fixed bugs compared to 7.2.6 see the list of bugs fixed in the release candidates of 7.2.7 (that's a total of 44+ bugs): https://wiki.documentfoundation.org/Releases/7.2.7/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.2.7/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1617/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 44+ bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972150] Re: Login screen freezes and sometimes shows artifacts
Oh maybe you just mean password entry doesn't work when the dock etc is visible? -- 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/1972150 Title: Login screen freezes and sometimes shows artifacts Status in gnome-shell package in Ubuntu: Incomplete Bug description: Sometimes when unlocking, it doesn't accept the correct password and doesn't show any errors, just keeps spinning and I have to press "escape" twice to be able to enter the password in the text box again, and this behavior keeps like that until I restart gdm from another TTY or reboot. Sometimes while switching TTY's, it shows artifacts like the screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon May 9 09:04:10 2022 InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) modified.conffile..etc.pam.d.gdm-password: [modified] mtime.conffile..etc.pam.d.gdm-password: 2022-02-19T02:26:10.814729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972150] Re: Login screen freezes and sometimes shows artifacts
Can you clarify what artifacts you see that are not bug 1882353? -- 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/1972150 Title: Login screen freezes and sometimes shows artifacts Status in gnome-shell package in Ubuntu: Incomplete Bug description: Sometimes when unlocking, it doesn't accept the correct password and doesn't show any errors, just keeps spinning and I have to press "escape" twice to be able to enter the password in the text box again, and this behavior keeps like that until I restart gdm from another TTY or reboot. Sometimes while switching TTY's, it shows artifacts like the screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon May 9 09:04:10 2022 InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) modified.conffile..etc.pam.d.gdm-password: [modified] mtime.conffile..etc.pam.d.gdm-password: 2022-02-19T02:26:10.814729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972150] Re: Login screen freezes and sometimes shows artifacts
The artifact issue is exactly as #1882353 But when it doesn't accept the correct password is something different. This can happen also without the artifacts. -- 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/1972150 Title: Login screen freezes and sometimes shows artifacts Status in gnome-shell package in Ubuntu: Incomplete Bug description: Sometimes when unlocking, it doesn't accept the correct password and doesn't show any errors, just keeps spinning and I have to press "escape" twice to be able to enter the password in the text box again, and this behavior keeps like that until I restart gdm from another TTY or reboot. Sometimes while switching TTY's, it shows artifacts like the screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon May 9 09:04:10 2022 InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) modified.conffile..etc.pam.d.gdm-password: [modified] mtime.conffile..etc.pam.d.gdm-password: 2022-02-19T02:26:10.814729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927100] Update Released
The verification of the Stable Release Update for gvfs 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 gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Focal: Fix Released Bug description: [Description/Impact] glib GFileMonitors can cause deadlocks if not explicitly cancelled before unref-ing (as of Dec 2021; see https://gitlab.gnome.org/GNOME/glib/-/issues/1941). In gvfs <1.46.2, gvfsd-trash can cause this deadlock, leading to 25s delays in spawning gtk+ dialogs system-wide. The best userspace workaround is explicitly pkill-ing gvfsd-trash at a sometimes frequent interval. This issue was reported and fixed in gvfs issue: https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 commit: https://gitlab.gnome.org/GNOME/gvfs/-/commit/dc21a0948bcbe8a6d79d674bd1e4d63ded57d340 merge: https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 [Test Case] To my knowledge, there is not a 100% reproducer for gvfs from userspace as this is a probable lock-ordering issue in lower-level code. https://gitlab.gnome.org/GNOME/glib/-/issues/1941 contains a reproducer for the underlying glib issue. User reports of gvfsd-trash manifesting this deadlock exist for Focal and Focal-based distributions, and it has been acknowledged and worked-around in gvfs. See: https://forums.linuxmint.com/viewtopic.php?f=47=328966 (Linux Mint forums) https://github.com/linuxmint/nemo/issues/2497 (Linux Mint nemo -- file manager) https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 (gvfs bug report, includes diagnosis and stacktrace showing the gvfsd-trash thread) The code change patched-in here has propagated to various other projects. See: https://bugs.launchpad.net/ubuntu/+source/libxmlb/+bug/1890313 https://github.com/fwupd/fwupd/issues/2350 [Regression Potential] This patch explicitly cancels GFileMonitors before "unreferencing" them to workaround a known glib issue. Absent any currently-unknown issues with the GFileMonitor framework, code added by this patch should be entirely within valid usage of GFileMonitors, is already present in gvfs releases in wide distribution, and, at worst, should become superfluous if/when the underlying glib issue is fixed. In the event that gvfsd-trash had some (currently unknown) mismanagement of its file watchers, it's possible that attempting to cancel an invalid monitor might behave differently than unref-ing it (which was already happening), but, this scenario would likely be bad either way. [Original Description] On Ubuntu Mate 20.04. Sometime the Open and Save dialogs in GTK applications will over 20 seconds to display. I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which suggested this due to gvfsd-trash, and running `killall gvfsd-trash` which does temporary solve the problem. The issue is apparently fixed in gvfs 1.46.2 Please could 1.46.2 or the fix https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
I'm experiencing this issue as well on Ubuntu 22.04. ** Attachment added: "photo_2022-05-08_20-10-49 (1).jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+attachment/5587864/+files/photo_2022-05-08_20-10-49%20%281%29.jpg -- 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/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: This is a very serious security issue: When I lock my desktop with SUPER (windows) + L my screen gets locked and goes to black. Sometimes when I return to my PC and move my mouse to turn my screen back on I notice that the Ubuntu Dock + the Top Bar are accessible from the lockscreen. I unfortunately can't remember if they were accessible from the moment I locked the screen or became accessible after returning from fade to black. (This is not the first time this issue happened.) I was able to open the settings menu from the top bar and use all indicators. You can actually start the programs in the Ubuntu Dock and give keyboard inputs to them. For example I was able to start the terminal emulator from the lock screen and run firefox and other applications. So an attacker could run arbitrary commands with user privileges from the lockscreen! The indicators drop down menus were fully visible on the lock screen while the Dock applications remained hidden "behind" the lockscreen (however still accessible via keyboard as described above). I have attached a screenshot of the bug. I unfortunately had no camera at hand to film me running terminal commands. Please contact me if you need additional information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 13:35:28 2020 InstallationDate: Installed on 2015-12-22 (1627 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927100] Re: Slow file dialogs, open and save
This bug was fixed in the package gvfs - 1.44.1-1ubuntu1.1 --- gvfs (1.44.1-1ubuntu1.1) focal; urgency=medium * debian/patches/fix-trashd-hang.patch: avoids deadlock in trashd that can cause gtk file dialogs to hang system-wide (LP: #1927100) -- David Buckmaster Tue, 21 Dec 2021 01:04:36 -0500 ** Changed in: gvfs (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Focal: Fix Released Bug description: [Description/Impact] glib GFileMonitors can cause deadlocks if not explicitly cancelled before unref-ing (as of Dec 2021; see https://gitlab.gnome.org/GNOME/glib/-/issues/1941). In gvfs <1.46.2, gvfsd-trash can cause this deadlock, leading to 25s delays in spawning gtk+ dialogs system-wide. The best userspace workaround is explicitly pkill-ing gvfsd-trash at a sometimes frequent interval. This issue was reported and fixed in gvfs issue: https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 commit: https://gitlab.gnome.org/GNOME/gvfs/-/commit/dc21a0948bcbe8a6d79d674bd1e4d63ded57d340 merge: https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 [Test Case] To my knowledge, there is not a 100% reproducer for gvfs from userspace as this is a probable lock-ordering issue in lower-level code. https://gitlab.gnome.org/GNOME/glib/-/issues/1941 contains a reproducer for the underlying glib issue. User reports of gvfsd-trash manifesting this deadlock exist for Focal and Focal-based distributions, and it has been acknowledged and worked-around in gvfs. See: https://forums.linuxmint.com/viewtopic.php?f=47=328966 (Linux Mint forums) https://github.com/linuxmint/nemo/issues/2497 (Linux Mint nemo -- file manager) https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 (gvfs bug report, includes diagnosis and stacktrace showing the gvfsd-trash thread) The code change patched-in here has propagated to various other projects. See: https://bugs.launchpad.net/ubuntu/+source/libxmlb/+bug/1890313 https://github.com/fwupd/fwupd/issues/2350 [Regression Potential] This patch explicitly cancels GFileMonitors before "unreferencing" them to workaround a known glib issue. Absent any currently-unknown issues with the GFileMonitor framework, code added by this patch should be entirely within valid usage of GFileMonitors, is already present in gvfs releases in wide distribution, and, at worst, should become superfluous if/when the underlying glib issue is fixed. In the event that gvfsd-trash had some (currently unknown) mismanagement of its file watchers, it's possible that attempting to cancel an invalid monitor might behave differently than unref-ing it (which was already happening), but, this scenario would likely be bad either way. [Original Description] On Ubuntu Mate 20.04. Sometime the Open and Save dialogs in GTK applications will over 20 seconds to display. I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which suggested this due to gvfsd-trash, and running `killall gvfsd-trash` which does temporary solve the problem. The issue is apparently fixed in gvfs 1.46.2 Please could 1.46.2 or the fix https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927100] Re: Slow file dialogs, open and save
Thank you for taking the time to do this! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Focal: Fix Released Bug description: [Description/Impact] glib GFileMonitors can cause deadlocks if not explicitly cancelled before unref-ing (as of Dec 2021; see https://gitlab.gnome.org/GNOME/glib/-/issues/1941). In gvfs <1.46.2, gvfsd-trash can cause this deadlock, leading to 25s delays in spawning gtk+ dialogs system-wide. The best userspace workaround is explicitly pkill-ing gvfsd-trash at a sometimes frequent interval. This issue was reported and fixed in gvfs issue: https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 commit: https://gitlab.gnome.org/GNOME/gvfs/-/commit/dc21a0948bcbe8a6d79d674bd1e4d63ded57d340 merge: https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 [Test Case] To my knowledge, there is not a 100% reproducer for gvfs from userspace as this is a probable lock-ordering issue in lower-level code. https://gitlab.gnome.org/GNOME/glib/-/issues/1941 contains a reproducer for the underlying glib issue. User reports of gvfsd-trash manifesting this deadlock exist for Focal and Focal-based distributions, and it has been acknowledged and worked-around in gvfs. See: https://forums.linuxmint.com/viewtopic.php?f=47=328966 (Linux Mint forums) https://github.com/linuxmint/nemo/issues/2497 (Linux Mint nemo -- file manager) https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 (gvfs bug report, includes diagnosis and stacktrace showing the gvfsd-trash thread) The code change patched-in here has propagated to various other projects. See: https://bugs.launchpad.net/ubuntu/+source/libxmlb/+bug/1890313 https://github.com/fwupd/fwupd/issues/2350 [Regression Potential] This patch explicitly cancels GFileMonitors before "unreferencing" them to workaround a known glib issue. Absent any currently-unknown issues with the GFileMonitor framework, code added by this patch should be entirely within valid usage of GFileMonitors, is already present in gvfs releases in wide distribution, and, at worst, should become superfluous if/when the underlying glib issue is fixed. In the event that gvfsd-trash had some (currently unknown) mismanagement of its file watchers, it's possible that attempting to cancel an invalid monitor might behave differently than unref-ing it (which was already happening), but, this scenario would likely be bad either way. [Original Description] On Ubuntu Mate 20.04. Sometime the Open and Save dialogs in GTK applications will over 20 seconds to display. I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which suggested this due to gvfsd-trash, and running `killall gvfsd-trash` which does temporary solve the problem. The issue is apparently fixed in gvfs 1.46.2 Please could 1.46.2 or the fix https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center
could you provide some details on the screens configuration you are using? -- 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/1972037 Title: Stack Overflow - gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Program: gnome-control-center Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) OS: ubuntu 20.04.4 LTS GNOME Version: 3.36.8 (ubuntu default download) Windowing System: X11 Graphics: GeForce 8400GS/PCIe/SSE2 Driver: Using NVIDIA binary driver version 340.108 Source: download version from ubuntu Steps to reproduce: Reset GNOME settings with: dconf reset -f /org/gnome/control-center/ Open GNOME Settings with: /usr/bin/gnome-control-center Click on "Displays" and receive: Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Segmentation fault (core dumped) Repeated using gdb with package symbols. Output of "bt -full" in attachment (with a few comments). (Submitted to gnome.org, but they said it is out of date and not supported by them.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 6 20:38:55 2022 InstallationDate: Installed on 2011-07-11 (3952 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center
Thank you for your bug report, the log has those warnings which is weird Xlib: extension "RANDR" missing on display ":0". could be somehow due to the nvidia drivers ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1972037 Title: Stack Overflow - gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Program: gnome-control-center Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) OS: ubuntu 20.04.4 LTS GNOME Version: 3.36.8 (ubuntu default download) Windowing System: X11 Graphics: GeForce 8400GS/PCIe/SSE2 Driver: Using NVIDIA binary driver version 340.108 Source: download version from ubuntu Steps to reproduce: Reset GNOME settings with: dconf reset -f /org/gnome/control-center/ Open GNOME Settings with: /usr/bin/gnome-control-center Click on "Displays" and receive: Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Segmentation fault (core dumped) Repeated using gdb with package symbols. Output of "bt -full" in attachment (with a few comments). (Submitted to gnome.org, but they said it is out of date and not supported by them.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 6 20:38:55 2022 InstallationDate: Installed on 2011-07-11 (3952 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972077] Re: cursor sizes "larger" and "largest" are as big as "large"
** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1972077 Title: cursor sizes "larger" and "largest" are as big as "large" Status in gnome-control-center package in Ubuntu: Invalid Bug description: If you set the cursor size to "larger" or "largest" in the accessibility options, it is as large as "large" and doesn't get any larger, despite the clickable images in the popup-dialog showing larger cursors for the different options. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun May 8 02:31:54 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-11-25 (894 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-05-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
