[Desktop-packages] [Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
> I've always thought the generic name is useful because it potentially allows multiple desktop environments to share a single layout... Assuming that didn't break any of them. monitors.xml generated by GNOME is incompatible with monitors.xml generated by MATE (see file layouts in the top post), which is indicated in the title of this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops Status in Mutter: Unknown Status in mutter package in Ubuntu: Opinion Bug description: Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028438] Re: gnome-control-center crash
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. 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-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028438 Title: gnome-control-center crash Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Suddenly today, while doing a backup (rsync) system started going to sleep... I know I had my setting set to not suspend, never to go to screensaver. Went to ope "Settings"... Settings loaded fine (then). Selected "Power". Settings crashed, and opened Bug Report dialog, but on "Send", that also crashed. "Settings" can no longer open at all. Starts to load, at least by the status in the upper bar of screen, then goes away. In 'top', I can see it running while it is trying to start (as gnome-control-center)... Then goes away. Have tried to re- install it, same problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Jul 22 12:28:06 2023 InstallationDate: Installed on 2021-09-23 (667 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-08-17 (339 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
I've always thought the generic name is useful because it potentially allows multiple desktop environments to share a single layout... Assuming that didn't break any of them. Regardless, this isn't the place to discuss such a change. The discussion should stay in https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 ** Package changed: gnome-control-center (Ubuntu) => mutter (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2919 https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: New => Opinion ** Changed in: mutter (Ubuntu) Importance: Undecided => Wishlist -- 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/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops Status in Mutter: Unknown Status in mutter package in Ubuntu: Opinion Bug description: Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- Mailing
[Desktop-packages] [Bug 2028438] Re: gnome-control-center crash
Further. When this originally happened, this was while checking a strange occurrence of the laptop going into hibernation... When all settings in the BIOS is set to not go to sleep... And everything in dconf set not to go to sleep. I don't know if this is related, but... It is still going to sleep. And Settings will not start. -- 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/2028438 Title: gnome-control-center crash Status in gnome-control-center package in Ubuntu: New Bug description: Suddenly today, while doing a backup (rsync) system started going to sleep... I know I had my setting set to not suspend, never to go to screensaver. Went to ope "Settings"... Settings loaded fine (then). Selected "Power". Settings crashed, and opened Bug Report dialog, but on "Send", that also crashed. "Settings" can no longer open at all. Starts to load, at least by the status in the upper bar of screen, then goes away. In 'top', I can see it running while it is trying to start (as gnome-control-center)... Then goes away. Have tried to re- install it, same problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Jul 22 12:28:06 2023 InstallationDate: Installed on 2021-09-23 (667 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-08-17 (339 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020851] Re: Monitor setup via USB-C dock reset by gnome randomly
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020851 Title: Monitor setup via USB-C dock reset by gnome randomly Status in gnome-shell package in Ubuntu: Expired Bug description: When using my intel based HP Dragonfly laptop on a USB-C Dock (thunderbolt) gnome randomly forgets my 3 screen setup configuration (display rotation and position) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 26 08:28:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-22 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 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/2020851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979891] Re: Firefox becomes unusable when adjusting window size
I have the same problem -- 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/1979891 Title: Firefox becomes unusable when adjusting window size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: OS version: Ubuntu 22.04 LTS Firefox version: 1:1snap1-0ubuntu2 - 101.0.1 (64-bit) Sometimes when I adjust the size of a Firefox window, that window becomes messed up: the contents don't fill the window, not all the controls are visible, and clicks are offset, so if I click on one spot, the window behaves as if I clicked on a different spot (so it's impossible to use Firefox in that window anymore). I seem to remember being able to fix this by dragging and dropping the window onto a different monitor or workspace in the GNOME Activities view, but I'm currently experiencing the problem and that is not helping. I took a screenshot of what's currently going on (attached) which happened when I tried to maximize the window. This is on a laptop with an external monitor that I'm using in portrait mode, via a USB-C connection that's converted to HDMI. I had plugged in to the external monitor a few minutes before this happens, and plugging in or possibly unplugging seems to make this bug more likely. This is a relatively new problem, starting within the last few weeks. (Maybe after I switched to the snap version of Firefox? I guess that was when I upgraded from the previous LTS version of Ubuntu.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 25 15:23:13 2022 DistUpgraded: 2022-05-27 14:03:05,108 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-39-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-11-23 (1309 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-27 (29 days ago) dmi.bios.date: 03/22/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd03/22/2022:br1.19:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 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/firefox/+bug/1979891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026886] Re: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
Have you tried running Chrome in native Wayland mode? Does it make a difference to this bug? chrome://flags/#ozone-platform-hint Change the setting “Preferred Ozone platform” to “Wayland”, then click Relaunch. -- 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/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 Status in mutter package in Ubuntu: Triaged Bug description: This morning, I upgraded gnome-shell and gnome-shell-common from 42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer renders properly. Notice the missing image header on the Ubuntu website and the garbled right click menu here: https://i.imgur.com/BPnqfVG.png I downgraded gnome-shell and gnome-shell-common version to 42.0-2ubuntu1, restarted gnome, and the rendering issues went away: https://i.imgur.com/CzEPgqY.png I upgraded gnome-shell and gnome-shell-common again to the latest and the rendering issues came back. Going to chrome://settings/system and disabling hardware acceleration fixes the rendering issues (but now I don't have hardware acceleration). I'm running the latest stable version of chrome which was released a few weeks ago: 114.0.5735.198 --- $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 (phased 40%) 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028711] [NEW] Feature Request: out-of-date browser notification
Public bug reported: On the top right side of the Chromium tab bar, could you display the following red text watermark, if the browser is out-of-date: “This version is NOT secure. Update to stay secure.” ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2028711 Title: Feature Request: out-of-date browser notification Status in chromium-browser package in Ubuntu: New Bug description: On the top right side of the Chromium tab bar, could you display the following red text watermark, if the browser is out-of-date: “This version is NOT secure. Update to stay secure.” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` The screen resolution is used directly (no need to log out). However, when you switch to the other desktop environment, the screen resolution is reset because their setup in monitors.xml is different. ## Links to bug reports - GNOME https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2579 + GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 - ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` - The screen resolution is used directly (no need to log out). However, - when you switch to the other desktop environment, the screen resolution - is reset because their setup in monitors.xml is different. + Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): + * Log into GNOME + * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` + * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2)
[Desktop-packages] [Bug 2028710] [NEW] Feature Request: Browser not up-to-date notification
Public bug reported: On the top right side of the Firefox tab bar, could you display the following red text watermark, if the browser is out-of-date: “This version is NOT secure. Update to stay secure.” ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/2028710 Title: Feature Request: Browser not up-to-date notification Status in firefox package in Ubuntu: New Bug description: On the top right side of the Firefox tab bar, could you display the following red text watermark, if the browser is out-of-date: “This version is NOT secure. Update to stay secure.” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2028710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018134] Re: [XMG PRO (E23), Realtek ALC1220, Speaker, Internal] No sound at all on either built in speakers, headphones or HDMI audio. Multiple reinstalls of alsa and others,
This workaround fixed the issue for me on the exact same laptop model: https://askubuntu.com/a/1423598 echo "options snd-hda-intel model=clevo-p950" | sudo tee -a /etc/modprobe.d/alsa-base.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2018134 Title: [XMG PRO (E23), Realtek ALC1220, Speaker, Internal] No sound at all on either built in speakers, headphones or HDMI audio. Multiple reinstalls of alsa and others, speaker levels in settings are moving yet no sound created Status in alsa-driver package in Ubuntu: New Bug description: In settings when selecting the built in audio the levels are moving and it thinks it's outputting sound, but nothing. Same results when using headphones or as a troubleshooting I attempted to use the hdmi audio out as well. Already tried reinstalling alsa and pulseaudio, to no effect. When running lspci -v | grep -A7 -i "audio" I get the following audio devices. 00:1f.3 Audio device: Intel Corporation Device 7a50 (rev 11) Subsystem: CLEVO/KAPOK Computer Device d702 Flags: bus master, fast devsel, latency 32, IRQ 204, IOMMU group 14 Memory at 620313 (64-bit, non-prefetchable) [size=16K] Memory at 620300 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 01:00.1 Audio device: NVIDIA Corporation Device 22bd (rev a1) Subsystem: NVIDIA Corporation Device Physical Slot: 1 Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 15 Memory at 7400 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrik 3084 F pulseaudio /dev/snd/controlC1: patrik 3084 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 11:07:13 2023 InstallationDate: Installed on 2023-04-27 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrik 3084 F pulseaudio /dev/snd/controlC1: patrik 3084 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [XMG PRO (E23), Realtek ALC1220, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2023 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: PD5x_7xSNC_SND_SNE dmi.board.vendor: NB01 dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: N/A dmi.ec.firmware.release: 7.4 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08RTR1:bd04/12/2023:br7.8:efr7.4:svnSchenkerTechnologiesGmbH:pnXMGPRO(E23):pvrNotApplicable:rvnNB01:rnPD5x_7xSNC_SND_SNE:rvrNotApplicable:cvnSchenkerTechnologiesGmbH:ct10:cvrN/A:skuXPR15E23/XPR17E23: dmi.product.name: XMG PRO (E23) dmi.product.sku: XPR15E23 / XPR17E23 dmi.product.version: Not Applicable dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2018134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028698] [NEW] desktop freezes when copying file to android phone
Public bug reported: If you try to copy a file named a:b.m4b using the nautilus file manager to a USB-connected Android phone in MTP mode, the desktop will freeze until you disconnect the USB cable. Then you'll get an error from nautilus: "Fehler beim Kopieren von »a:b.m4b«. Beim Kopieren der Datei nach mtp://Google_Pixel_7_291... mer%Speicher/Audiobooks ist ein Fehler aufgetreten libmtp-Fehler: Could not send object." This happens when the file to be copied contains the colon symbol : ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs-backends 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jul 25 21:46:45 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-08-20 (704 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: gvfs UpgradeStatus: Upgraded to jammy on 2022-09-10 (318 days ago) ** Affects: gvfs (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 gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2028698 Title: desktop freezes when copying file to android phone Status in gvfs package in Ubuntu: New Bug description: If you try to copy a file named a:b.m4b using the nautilus file manager to a USB-connected Android phone in MTP mode, the desktop will freeze until you disconnect the USB cable. Then you'll get an error from nautilus: "Fehler beim Kopieren von »a:b.m4b«. Beim Kopieren der Datei nach mtp://Google_Pixel_7_291... mer%Speicher/Audiobooks ist ein Fehler aufgetreten libmtp-Fehler: Could not send object." This happens when the file to be copied contains the colon symbol : ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs-backends 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jul 25 21:46:45 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-08-20 (704 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: gvfs UpgradeStatus: Upgraded to jammy on 2022-09-10 (318 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2028698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982483]
Oops hit enter too soon. Anyway, the patch doesn't fix anything at all. :-( Just put some things I found in the RtHDDump.txt in a patch for reference... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio and newer kernels up to 5.19-rc6. 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x610500-0x61050f (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v8086d7AD0sv103Csd89E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[3.582359] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[3.582362] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[3.582364] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 <6>[3.582366] snd_hda_codec_realtek hdaudioC0D0:inputs: <6>[3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Here is a kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=216139 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernst 1560 F pulseaudio /dev/snd/controlC0: ernst 1560 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (143 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1006-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1006.6-oem 6.0.0 RelatedPackageVersions: linux-restricted-modules-6.0.0-1006-oem N/A linux-backports-modules-6.0.0-1006-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy wayland-session Uname: Linux 6.0.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx dmi.product.sku: 661Q7EA#UUW dmi.sys.vendor: HP modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1982483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982483]
Created attachment 304697 Broken patch, doesn -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio and newer kernels up to 5.19-rc6. 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x610500-0x61050f (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v8086d7AD0sv103Csd89E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[3.582359] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[3.582362] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[3.582364] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 <6>[3.582366] snd_hda_codec_realtek hdaudioC0D0:inputs: <6>[3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Here is a kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=216139 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernst 1560 F pulseaudio /dev/snd/controlC0: ernst 1560 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (143 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1006-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1006.6-oem 6.0.0 RelatedPackageVersions: linux-restricted-modules-6.0.0-1006-oem N/A linux-backports-modules-6.0.0-1006-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy wayland-session Uname: Linux 6.0.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx dmi.product.sku: 661Q7EA#UUW dmi.sys.vendor: HP modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1982483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028694] Re: software app crashes on start
*** This bug is a duplicate of bug 2028071 *** https://bugs.launchpad.net/bugs/2028071 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2028071, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2028694/+attachment/5688359/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2028694/+attachment/5688361/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2028694/+attachment/5688362/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 2028071 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2028694 Title: software app crashes on start Status in gnome-software package in Ubuntu: New Bug description: Mantic, applied 434 software updates, rebooted. Also synaptic shows Gnome suite as AutoRemovable ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-software 44.3-1ubuntu1 Uname: Linux 6.3.0-7-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 25 15:00:18 2023 ExecutablePath: /usr/bin/gnome-software ExecutableTimestamp: 1689178851 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcCwd: /home/hcmeyer ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-software UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2028694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982483]
Ah no actually Wid=18 differs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio and newer kernels up to 5.19-rc6. 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x610500-0x61050f (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v8086d7AD0sv103Csd89E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[3.582359] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[3.582362] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[3.582364] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 <6>[3.582366] snd_hda_codec_realtek hdaudioC0D0:inputs: <6>[3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Here is a kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=216139 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernst 1560 F pulseaudio /dev/snd/controlC0: ernst 1560 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (143 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1006-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1006.6-oem 6.0.0 RelatedPackageVersions: linux-restricted-modules-6.0.0-1006-oem N/A linux-backports-modules-6.0.0-1006-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy wayland-session Uname: Linux 6.0.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx dmi.product.sku: 661Q7EA#UUW dmi.sys.vendor: HP modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1982483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982483]
The basic pin-config looks perfect... Wid=12 Codec=90A60130 Drv=90A60130 Loc= Wid=13 Codec=4000 Drv=4000 Loc= Wid=14 Codec=41F0 Drv=41F0 Loc= Wid=15 Codec=41F0 Drv=41F0 Loc= Wid=16 Codec=41F0 Drv=41F0 Loc= Wid=17 Codec=90170110 Drv=90170110 Loc= Wid=18 Codec=41F0 Drv=81D111F0 Loc= Wid=19 Codec=03A11040 Drv=03A11040 Loc= Wid=1A Codec=41F0 Drv=41F0 Loc= Wid=1B Codec=41F0 Drv=41F0 Loc= Wid=1D Codec=4061 Drv=4061 Loc= Wid=1E Codec=41F0 Drv=41F0 Loc= Wid=1F Codec=41F0 Drv=41F0 Loc= Wid=21 Codec=03211020 Drv=03211020 Loc= is the same as in alsa-info. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio and newer kernels up to 5.19-rc6. 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x610500-0x61050f (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v8086d7AD0sv103Csd89E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[3.582359] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[3.582362] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[3.582364] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 <6>[3.582366] snd_hda_codec_realtek hdaudioC0D0:inputs: <6>[3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Here is a kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=216139 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernst 1560 F pulseaudio /dev/snd/controlC0: ernst 1560 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (143 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1006-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1006.6-oem 6.0.0 RelatedPackageVersions: linux-restricted-modules-6.0.0-1006-oem N/A linux-backports-modules-6.0.0-1006-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy wayland-session Uname: Linux 6.0.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP
[Desktop-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
** Changed in: ibus Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: Fix Released Status in ibus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026886] Re: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
awesome, thank you. I will keep the flag set :-) -- 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/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 Status in mutter package in Ubuntu: Triaged Bug description: This morning, I upgraded gnome-shell and gnome-shell-common from 42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer renders properly. Notice the missing image header on the Ubuntu website and the garbled right click menu here: https://i.imgur.com/BPnqfVG.png I downgraded gnome-shell and gnome-shell-common version to 42.0-2ubuntu1, restarted gnome, and the rendering issues went away: https://i.imgur.com/CzEPgqY.png I upgraded gnome-shell and gnome-shell-common again to the latest and the rendering issues came back. Going to chrome://settings/system and disabling hardware acceleration fixes the rendering issues (but now I don't have hardware acceleration). I'm running the latest stable version of chrome which was released a few weeks ago: 114.0.5735.198 --- $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 (phased 40%) 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028677] [NEW] simple scan does not find the scanner
Public bug reported: simple scan does not find the scanner but scan seems ok. DEBUG: scanner.vala:348: sane_get_devices () -> SANE_STATUS_GOOD On same PC different partition scan works fine. corrado@corrado-n16-mm-0722:~$ simple-scan -d [+0.00s] DEBUG: simple-scan.vala:2015: Starting simple-scan 44.0, PID=12501 [+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after threads are created [+0.08s] DEBUG: app-window.vala:2002: Loading state from /home/corrado/.config/simple-scan/state [+0.08s] DEBUG: app-window.vala:1981: Restoring window to 852x656 pixels [+0.10s] DEBUG: scanner.vala:1619: sane_init () -> SANE_STATUS_GOOD [+0.10s] DEBUG: scanner.vala:1625: SANE version 1.2.1 [+0.10s] DEBUG: scanner.vala:1686: Requesting redetection of scan devices [+0.10s] DEBUG: scanner.vala:863: Processing request [+0.24s] DEBUG: app-window.vala:2078: Saving state to /home/corrado/.config/simple-scan/state [+0.40s] DEBUG: app-window.vala:2078: Saving state to /home/corrado/.config/simple-scan/state [+7.62s] DEBUG: scanner.vala:348: sane_get_devices () -> SANE_STATUS_GOOD [+7.62s] DEBUG: scanner.vala:1686: Requesting redetection of scan devices [+7.62s] DEBUG: scanner.vala:863: Processing request [+7.78s] DEBUG: app-window.vala:2078: Saving state to /home/corrado/.config/simple-scan/state [+12.93s] DEBUG: scanner.vala:348: sane_get_devices () -> SANE_STATUS_GOOD [+13.03s] DEBUG: app-window.vala:2078: Saving state to /home/corrado/.config/simple-scan/state corrado@corrado-n16-mm-0722:~$ lsusb Bus 004 Device 002: ID 2109:0815 VIA Labs, Inc. USB3.0 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter Bus 003 Device 004: ID 3938:1191 2.4G Wireless Mouse Bus 003 Device 002: ID 2109:2815 VIA Labs, Inc. USB2.0 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc. Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 006: ID 145f:02a9 Trust Trust Wireless Mouse Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 03f0:c911 HP, Inc Officejet 2620 series Bus 001 Device 002: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub corrado@corrado-n16-mm-0722:~$ inxi -SCGx System: Host: corrado-n16-mm-0722 Kernel: 6.3.0-7-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 44.3 Distro: Ubuntu 23.10 (Mantic Minotaur) CPU: Info: quad core model: 12th Gen Intel Core i3-12100 bits: 64 type: MT MCP arch: Alder Lake rev: 5 cache: L1: 320 KiB L2: 5 MiB L3: 12 MiB Speed (MHz): avg: 3300 min/max: 800/5500 cores: 1: 3300 2: 3300 3: 3300 4: 3300 5: 3300 6: 3300 7: 3300 8: 3300 bogomips: 52838 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Alder Lake-S GT1 [UHD Graphics 730] vendor: ASUSTeK driver: i915 v: kernel arch: Gen-12.2 bus-ID: 00:02.0 Device-2: Logitech QuickCam Pro 9000 driver: snd-usb-audio,uvcvideo type: USB bus-ID: 1-1:2 Display: wayland server: X.Org v: 1.23.1.1 with: Xwayland v: 23.1.1 compositor: gnome-shell driver: dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 23.1.3-1ubuntu1 renderer: Mesa Intel UHD Graphics 730 (ADL-S GT1) direct-render: Yes corrado@corrado-n16-mm-0722:~$ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: simple-scan 44.0-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 25 15:55:15 2023 InstallationDate: Installed on 2023-07-22 (2 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230722) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic root=UUID=4a1c8cba-f79d-48cf-83f0-d8290999f2eb ro quiet splash vt.handoff=7 SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2022 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: PRIME H610M-E D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd04/01/2022:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610M-ED4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by
[Desktop-packages] [Bug 2028674] [NEW] Automatically switch profiles based on plugged-in status
Public bug reported: As of now there is no option to switch power profiles automatically, based on the status (plugged-in or not) of the device. It would be a very useful feature, and would work around the requirement to create user scripts and download gnome-extensions. E.g: https://extensions.gnome.org/extension/5575/power-profile-switcher/ ** Affects: power-profiles-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2028674 Title: Automatically switch profiles based on plugged-in status Status in power-profiles-daemon package in Ubuntu: New Bug description: As of now there is no option to switch power profiles automatically, based on the status (plugged-in or not) of the device. It would be a very useful feature, and would work around the requirement to create user scripts and download gnome-extensions. E.g: https://extensions.gnome.org/extension/5575/power-profile-switcher/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2028674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987225] Re: I open tweaks, set my icons to Breathe. Then I go to settings for something and my icons are rest to default icons
*** This bug is a duplicate of bug 1968213 *** https://bugs.launchpad.net/bugs/1968213 It is advised to select the best business for the task and, more crucially, high-quality supplies. Why use subpar materials when you can select top names like Farrow and Ball, Dulux, Johnstone, or Sadolin? We can only get the best effects if we use the proper paint.https://www.lgcdecorators.co.uk/ -- 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/1987225 Title: I open tweaks, set my icons to Breathe. Then I go to settings for something and my icons are rest to default icons Status in gnome-control-center package in Ubuntu: New Bug description: This started happening after my upgrade from Ubuntu 20.04 to Ubuntu 22.04 I open tweaks, set my icons to a custom theme. Then I go to settings > appearanace to adjust dock icon size and my dock and Desktop icons are reset to default icons. This happens every time I open settings>appearance. It overrides gnome-tweaks icon settings. I expected to be able to change the dock icon size without my icon theme being changed and my icon settings to stay as I had set them in Tweaks. I can reset the icon theme in Tweaks and they stay set after reboot. Then if I open settings again and use appearance feature of any kind my Tweaks icon settings revert to Yaru. I have seen many references to this bug on Google. It is annoying to many Ubuntu users! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 13:56:51 2022 InstallationDate: Installed on 2022-06-03 (79 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to jammy on 2022-08-21 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
Kinetic has now reached end-of-life. There is nothing else to sponsor in this bug for now. I am unsubscribing ubuntu-security-sponsors. If a new debdiff is attached for sponsoring, please re-subscribe the team. Thanks! ** Changed in: nemo (Ubuntu Kinetic) Status: In Progress => Won't Fix ** Changed in: caja (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: Won't Fix Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: Won't Fix Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028653] Re: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher)
NP. You are welcome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2028653 Title: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher) Status in chromium-browser package in Ubuntu: Fix Committed Bug description: There is error in line 143. Probably left over from git merge: === >>> hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028653] Re: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher)
Ouch... Thank you for the report. I committed the fix and while the new snap isn't finished building, I rolled back the edge snap to the previous version. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2028653 Title: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher) Status in chromium-browser package in Ubuntu: Fix Committed Bug description: There is error in line 143. Probably left over from git merge: === >>> hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028653] Re: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher)
** Changed in: chromium-browser (Ubuntu) Status: New => Triaged ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2028653 Title: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher) Status in chromium-browser package in Ubuntu: Fix Committed Bug description: There is error in line 143. Probably left over from git merge: === >>> hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028653] [NEW] latest/edge (117.0.5897.3) not starting (issue in chromium.launcher)
Public bug reported: There is error in line 143. Probably left over from git merge: === >>> hwacc-dev ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2028653 Title: latest/edge (117.0.5897.3) not starting (issue in chromium.launcher) Status in chromium-browser package in Ubuntu: New Bug description: There is error in line 143. Probably left over from git merge: === >>> hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Sorry to hear you're still having problems.
Since the new issue has different symptoms on a different Ubuntu release
we should track it in a different bug. If you are still willing to use
Ubuntu then please open a new bug about the new issue. If the machine is
not booting (black screen) then try accessing the grub menu (tap Escape
or hold Shift during early boot) and select recovery mode. In recovery
mode please then run:
journalctl -b-1 > prevboot1.txt
journalctl -b-2 > prevboot2.txt
and attach the resulting text files to the new bug, not this one.
--
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/2023776
Title:
Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Currently using Nvidia driver 525, which is the "tested" and
recommended driver according to Ubuntu's additional driver tool (as of
this writing).
- manually resizing "files" windows = low fps and a little bit of
pixelation
- moving windows around = drop in fps every now and then
- opening the Gnome overview = sometimes buttery smooth 60fps but
sometimes stuttery low fps that takes time to "catch up" to smoothness
again
- resizing Chromium or Firefox window = low fps, glitchy window
behaviour etc.
How to fix it? Well, this is what I found works thus far:
- disable both "vsync" and "allow flipping" in Nvidia-settings
- now everything is buttery smooth again; all animations, apps, games
and more
- doing this will introduce lots of tearing on the Gnome desktop and
applications though
- then force full composition pipeline to get rid of the tearing by
adding this start-up line to Ubuntu's start-up applications: nvidia-
settings --assign CurrentMetaMode="nvidia-auto-select +0+0
{ForceFullCompositionPipeline=On}"
- Use Wayland alternatively: Wayland doesn't have any of these issues
at all, it's a buttery smooth fully vsynced experience ootb, but a
bunch of new problems arise instead: Can't set global hotkeys for
recording in OBS, OBS recording performance is pretty bad, Gnome
folder windows start flickering somestimes, Gnome windows glitch out
when trying to resize them manually, Steam flickering sometimes,
browsers such as Firefox and Chromium have to be set to Wayland mode
in order to solve stuttering video playback issues, Nvidia-settings is
missing a bunch of settings and features when compared to X11... and
more
Hard- and Software:
- Ubuntu 23.04
- Nvidia driver version 525 (tested) from Ubuntu's additional drivers tool
- Core i7 7700
- 32 GB DDR4 RAM
- Lenovo Nvidia RTX A2000 workstation GPU
- TWO fullHD monitors connected via display port
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 14 14:58:08 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-05-20 (24 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.1-0ubuntu1
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/mutter/+bug/2023776/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Please also try to keep each bug report concise and on a single topic.
You can log as many different bugs as you like.
--
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/2023776
Title:
Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Currently using Nvidia driver 525, which is the "tested" and
recommended driver according to Ubuntu's additional driver tool (as of
this writing).
- manually resizing "files" windows = low fps and a little bit of
pixelation
- moving windows around = drop in fps every now and then
- opening the Gnome overview = sometimes buttery smooth 60fps but
sometimes stuttery low fps that takes time to "catch up" to smoothness
again
- resizing Chromium or Firefox window = low fps, glitchy window
behaviour etc.
How to fix it? Well, this is what I found works thus far:
- disable both "vsync" and "allow flipping" in Nvidia-settings
- now everything is buttery smooth again; all animations, apps, games
and more
- doing this will introduce lots of tearing on the Gnome desktop and
applications though
- then force full composition pipeline to get rid of the tearing by
adding this start-up line to Ubuntu's start-up applications: nvidia-
settings --assign CurrentMetaMode="nvidia-auto-select +0+0
{ForceFullCompositionPipeline=On}"
- Use Wayland alternatively: Wayland doesn't have any of these issues
at all, it's a buttery smooth fully vsynced experience ootb, but a
bunch of new problems arise instead: Can't set global hotkeys for
recording in OBS, OBS recording performance is pretty bad, Gnome
folder windows start flickering somestimes, Gnome windows glitch out
when trying to resize them manually, Steam flickering sometimes,
browsers such as Firefox and Chromium have to be set to Wayland mode
in order to solve stuttering video playback issues, Nvidia-settings is
missing a bunch of settings and features when compared to X11... and
more
Hard- and Software:
- Ubuntu 23.04
- Nvidia driver version 525 (tested) from Ubuntu's additional drivers tool
- Core i7 7700
- 32 GB DDR4 RAM
- Lenovo Nvidia RTX A2000 workstation GPU
- TWO fullHD monitors connected via display port
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 14 14:58:08 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-05-20 (24 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.1-0ubuntu1
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/mutter/+bug/2023776/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971242] Autopkgtest regression report (cups/2.4.2-3ubuntu2.3)
All autopkgtests for the newly accepted cups (2.4.2-3ubuntu2.3) for lunar have
finished running.
The following regressions have been reported in tests triggered by the package:
cmake/3.25.1-1ubuntu1 (armhf)
foo2zjs/20200505dfsg0-2ubuntu3 (arm64)
libreoffice/4:7.5.4-0ubuntu0.23.04.1 (armhf)
samba/2:4.17.7+dfsg-1ubuntu1.1 (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#cups
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Committed
Status in cups source package in Lunar:
Fix Committed
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
** Attachment added: "Bildschirmfoto vom 2023-07-25 05-42-01.png"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688204/+files/Bildschirmfoto%20vom%202023-07-25%2005-42-01.png
--
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/2023776
Title:
Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Currently using Nvidia driver 525, which is the "tested" and
recommended driver according to Ubuntu's additional driver tool (as of
this writing).
- manually resizing "files" windows = low fps and a little bit of
pixelation
- moving windows around = drop in fps every now and then
- opening the Gnome overview = sometimes buttery smooth 60fps but
sometimes stuttery low fps that takes time to "catch up" to smoothness
again
- resizing Chromium or Firefox window = low fps, glitchy window
behaviour etc.
How to fix it? Well, this is what I found works thus far:
- disable both "vsync" and "allow flipping" in Nvidia-settings
- now everything is buttery smooth again; all animations, apps, games
and more
- doing this will introduce lots of tearing on the Gnome desktop and
applications though
- then force full composition pipeline to get rid of the tearing by
adding this start-up line to Ubuntu's start-up applications: nvidia-
settings --assign CurrentMetaMode="nvidia-auto-select +0+0
{ForceFullCompositionPipeline=On}"
- Use Wayland alternatively: Wayland doesn't have any of these issues
at all, it's a buttery smooth fully vsynced experience ootb, but a
bunch of new problems arise instead: Can't set global hotkeys for
recording in OBS, OBS recording performance is pretty bad, Gnome
folder windows start flickering somestimes, Gnome windows glitch out
when trying to resize them manually, Steam flickering sometimes,
browsers such as Firefox and Chromium have to be set to Wayland mode
in order to solve stuttering video playback issues, Nvidia-settings is
missing a bunch of settings and features when compared to X11... and
more
Hard- and Software:
- Ubuntu 23.04
- Nvidia driver version 525 (tested) from Ubuntu's additional drivers tool
- Core i7 7700
- 32 GB DDR4 RAM
- Lenovo Nvidia RTX A2000 workstation GPU
- TWO fullHD monitors connected via display port
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 14 14:58:08 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-05-20 (24 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.1-0ubuntu1
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/mutter/+bug/2023776/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Screenshots: Ubuntu 22.04.2 LTS, partial upgrade option after Nvidia
driver 535 went live.
** Attachment added: "Bildschirmfoto vom 2023-07-25 05-42-07.png"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688203/+files/Bildschirmfoto%20vom%202023-07-25%2005-42-07.png
--
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/2023776
Title:
Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Currently using Nvidia driver 525, which is the "tested" and
recommended driver according to Ubuntu's additional driver tool (as of
this writing).
- manually resizing "files" windows = low fps and a little bit of
pixelation
- moving windows around = drop in fps every now and then
- opening the Gnome overview = sometimes buttery smooth 60fps but
sometimes stuttery low fps that takes time to "catch up" to smoothness
again
- resizing Chromium or Firefox window = low fps, glitchy window
behaviour etc.
How to fix it? Well, this is what I found works thus far:
- disable both "vsync" and "allow flipping" in Nvidia-settings
- now everything is buttery smooth again; all animations, apps, games
and more
- doing this will introduce lots of tearing on the Gnome desktop and
applications though
- then force full composition pipeline to get rid of the tearing by
adding this start-up line to Ubuntu's start-up applications: nvidia-
settings --assign CurrentMetaMode="nvidia-auto-select +0+0
{ForceFullCompositionPipeline=On}"
- Use Wayland alternatively: Wayland doesn't have any of these issues
at all, it's a buttery smooth fully vsynced experience ootb, but a
bunch of new problems arise instead: Can't set global hotkeys for
recording in OBS, OBS recording performance is pretty bad, Gnome
folder windows start flickering somestimes, Gnome windows glitch out
when trying to resize them manually, Steam flickering sometimes,
browsers such as Firefox and Chromium have to be set to Wayland mode
in order to solve stuttering video playback issues, Nvidia-settings is
missing a bunch of settings and features when compared to X11... and
more
Hard- and Software:
- Ubuntu 23.04
- Nvidia driver version 525 (tested) from Ubuntu's additional drivers tool
- Core i7 7700
- 32 GB DDR4 RAM
- Lenovo Nvidia RTX A2000 workstation GPU
- TWO fullHD monitors connected via display port
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 14 14:58:08 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-05-20 (24 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.1-0ubuntu1
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/mutter/+bug/2023776/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Hello Daniel, I apologize for the huge delay, but I have been experiencing a number of show stopping issues that I have yet to recover from. As written above: After all the issues that I had with Ubuntu 23.04, I decided to "downgrade" to Ubuntu 22.04.2, which was working just fine at first, see comment above. I was using the recommended and "tested" Nvidia driver 525, which was the one that the Ubuntu additional drivers tool suggested. Recently Nvidia released the proprietary Nvidia driver version 535, which was made available via Ubuntu 22.04.2. So I ran the Ubuntu system updates utility like I usually would, in the hopes of Ubuntu picking up the newest Nvidia driver automatically, like it has always done in the past. Ubuntu did find and suggest to install the new Nvidia driver, but... Just like on Ubuntu 23.04, Ubuntu 22.04.2 also mentioned something about a "partial upgrade", see attached screenshots below. Trying to click on "continue" instead didn't offer any updates, so I went back to the "partial upgrade" option, because my system wasn't getting any updates whatsoever ever since this "issue" appeared out of nowhere. In the middle of the "partial upgrade" my 22.04.2 system went black, meaning all of my screens turned off randomly, and the computer would not react to any user input whatsoever. After being forced to perform a hard reboot, the computer did not want to boot, spitting out several "journal errors" during the boot process. I would like to mention that this was a fresh install of 22.04.2 - not a single ppa etc. was added manually - just a handful of native apps installed as Snap via the official Ubuntu Software Center (including Steam, also installed via the Ubuntu Software Center). I hardly used the system, because I was still in the process of transferring over the data that I had to recover from my busted 23.04 install. A few notes here: - this happened totally randomly - previous system updates were completed without any issues whatsoever - there were no issues whatsoever before the new Nvidia driver 535 - the partial upgrade option mentioned a bunch of Nvidia 535 modules to be installed - and the old 530 driver to be removed - and it also mentioned a ton of other things to be updated as well, including the kernel and a bunch of Ubuntu desktop files Digging around I found out that both this and the low latency kernel subject is a common and repeating issue: - https://askubuntu.com/questions/1443779/why-doesnt-this-software- updater-warning-tell-me-what-is-going-to-be-installed - https://www.reddit.com/r/Kubuntu/comments/14ndb7a/why_do_i_keep_getting_these_oracle_and_lowlatency/ - https://askubuntu.com/questions/1334791/not-all-updates-can-be- installed-in-software-updater - https://askubuntu.com/questions/725481/ubuntu-software-updater-not- all-updates-can-be-installed - https://www.google.com/search?channel=fs=ubuntu- sn=ubuntu+nvidia+partial+upgrade Verdict: Now I have to recover my freshly installed 22.04.2 system again, just like I did with 23.04 a few days ago. Since I don't have the time to troubleshoot this yet again, I am now forced to go for a clean install again, but I will be using a different distro this time around as it seems that even Ubuntu LTS has become highly unstable / unusable for Nvidia users. This is extremely aggravating to say the least. This entire ordeal will set me back another one or two weeks at the very least. Been an Ubuntu user for decades now, and recently switched from AMD to Nvidia gpu, and it's been nothing but trouble thus far, sadly. Using an AMD gpu was flawless for the most part, but on Nvidia it's one headache after another on Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023776 Title: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions Status in mutter package in Ubuntu: Incomplete Bug description: Currently using Nvidia driver 525, which is the "tested" and recommended driver according to Ubuntu's additional driver tool (as of this writing). - manually resizing "files" windows = low fps and a little bit of pixelation - moving windows around = drop in fps every now and then - opening the Gnome overview = sometimes buttery smooth 60fps but sometimes stuttery low fps that takes time to "catch up" to smoothness again - resizing Chromium or Firefox window = low fps, glitchy window behaviour etc. How to fix it? Well, this is what I found works thus far: - disable both "vsync" and "allow flipping" in Nvidia-settings - now everything is buttery smooth again; all animations, apps, games and more - doing this will introduce lots of tearing on the Gnome desktop and applications though - then force full composition pipeline to get rid of the tearing by adding this start-up line to Ubuntu's start-up applications: nvidia- settings --assign
[Desktop-packages] [Bug 2028610] Re: bring-to-front and send-to-back not working for some apps
*** This bug is a duplicate of bug 2015577 *** https://bugs.launchpad.net/bugs/2015577 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2015577, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: regression-release ** This bug has been marked a duplicate of bug 2015577 middle click to lower window no longer works for xwayland windows -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028610 Title: bring-to-front and send-to-back not working for some apps Status in mutter package in Ubuntu: New Bug description: Since I upgraded to Ubuntu 23.04, a number of my applications have stopped accepting bring-to-front (right click on the title bar) and send-to-back (middle click on the title bar). On the other hand, other apps (native Gnome apps seemingly) do still seem to work. Note I'm using X11 not Wayland. A set of apps I know do not work anymore, that used to work with Ubuntu 22.10 and below: * xterm * Emacs * Chrome * Slack * Spotify * VirtualBox manager Some apps that do still work: * Remmina * File Manager * gnome-terminal * Gnome Settings * Ubuntu Software There are many more in both categories. Please fix things so that I can use bring-to-front and send-to-back on all my apps again. Thanks! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21 Uname: Linux 5.14.0-1054-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 23:31:31 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2022-12-02 (234 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-06-04 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2028610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015577] Re: middle click to lower window no longer works for xwayland windows
** Tags added: regression-release -- 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/2015577 Title: middle click to lower window no longer works for xwayland windows Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: i have titlebar middle-click set to lower windows in Tweaks. In kinetic, this works for xwayland windows, while in lunar it no longer does. (native wayland gtk3 and gtk4 apps do appear to work though, which was a long time coming!) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xwayland 2:22.1.8-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Apr 7 08:54:02 2023 InstallationDate: Installed on 2019-08-17 (1329 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xwayland UpgradeStatus: Upgraded to lunar on 2023-04-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
Also I can easily reproduce by repeatedly calling this command: kdialog --passivepopup 'text' 5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Tested with Nvidia GPU 10de:2717. Disable restricted in jammy-updates
and jammy-security, which make Nvidia 525 unavailable. Add
/etc/customer_supported_gpus.json
{
"chips": [
{
"devid": "0x2717",
"name": "TEST 2717",
"branch": "510.60",
"feature": [
"runtimepm"
]
}
]
}
Type "ubuntu-driver list" in console did not show anything.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-failed verification-failed-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Fix Committed
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028610] [NEW] bring-to-front and send-to-back not working for some apps
Public bug reported: Since I upgraded to Ubuntu 23.04, a number of my applications have stopped accepting bring-to-front (right click on the title bar) and send-to-back (middle click on the title bar). On the other hand, other apps (native Gnome apps seemingly) do still seem to work. Note I'm using X11 not Wayland. A set of apps I know do not work anymore, that used to work with Ubuntu 22.10 and below: * xterm * Emacs * Chrome * Slack * Spotify * VirtualBox manager Some apps that do still work: * Remmina * File Manager * gnome-terminal * Gnome Settings * Ubuntu Software There are many more in both categories. Please fix things so that I can use bring-to-front and send-to-back on all my apps again. Thanks! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21 Uname: Linux 5.14.0-1054-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 23:31:31 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2022-12-02 (234 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-06-04 (50 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2028610 Title: bring-to-front and send-to-back not working for some apps Status in mutter package in Ubuntu: New Bug description: Since I upgraded to Ubuntu 23.04, a number of my applications have stopped accepting bring-to-front (right click on the title bar) and send-to-back (middle click on the title bar). On the other hand, other apps (native Gnome apps seemingly) do still seem to work. Note I'm using X11 not Wayland. A set of apps I know do not work anymore, that used to work with Ubuntu 22.10 and below: * xterm * Emacs * Chrome * Slack * Spotify * VirtualBox manager Some apps that do still work: * Remmina * File Manager * gnome-terminal * Gnome Settings * Ubuntu Software There are many more in both categories. Please fix things so that I can use bring-to-front and send-to-back on all my apps again. Thanks! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21 Uname: Linux 5.14.0-1054-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 23:31:31 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2022-12-02 (234 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-06-04 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2028610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
